Actions
action #155740
closedScripts CI pipelines fail due to timeout after many Job state of job ID xyz: scheduled, waiting messages
Start date:
2024-02-21
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Observation¶
https://gitlab.suse.de/openqa/scripts-ci/-/jobs/2298958
{"count":2,"failed":[],"ids":[13560656,13560657],"scheduled_product_id":2058111}
2 jobs have been created:
- http://openqa.suse.de/tests/13560656
- http://openqa.suse.de/tests/13560657
{"blocked_by_id":null,"id":13560656,"result":"none","state":"scheduled"}
Job state of job ID 13560656: scheduled, waiting …
{"blocked_by_id":null,"id":13560656,"result":"none","state":"scheduled"}
[...]
Job state of job ID 13560656: scheduled, waiting …
{"blocked_by_id":null,"id":13560656,"result":"none","state":"scheduled"}
Jo
ERROR: Job failed: execution took longer than 1h0m0s seconds
Suggestions¶
Updated by okurz 8 months ago
- Status changed from In Progress to Resolved
In https://gitlab.suse.de/openqa/scripts-ci/-/settings/ci_cd I set a timeout of 2d (up from 1h) as it can very well be that jobs stay scheduled for longer. Retriggered job as https://gitlab.suse.de/openqa/scripts-ci/-/jobs/2301281 which succeeded now within shorter time anyway.
Actions