-
Bug
-
Resolution: Fixed
-
Critical
-
3.8.3, 3.9
-
MOODLE_38_STABLE, MOODLE_39_STABLE
-
MOODLE_38_STABLE
-
MDL-68579-master -
Recently we have started to get a number of unexpected failures in various CI jobs. Apparently random scenarios.
Looking to logs we have seen that this seems to be the ultimate cause for many of them:
Execute scheduled task: Download available H5P content types from h5p.org (core\task\h5p_get_content_types_task)
|
... started 22:36:06. Current memory use 7.6MB.
|
|
Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/h5p/h5plib/v124/joubel/core/h5p.classes.php on line 896
|
^^^ normally with the cron execution step being the cause. Hence, any scenario / test running cron... is now susceptible to fail because of that.
This is about to avoid that problem, not sure if controlling the request time, if avoiding the execution or what (hopefully not by raising time limits because that may have a awful multiplicative effect in testing times).
That's the problem, anyway. Here there are some failed runs, as example:
- Testing discovered
-
MDL-68643 Change the calls to cron using Behat to calls to specific schedule task
- Open