Project

General

Profile

Actions

action #133556

open

[sporadic] bot-ng gitlab CI execution timeout or stuck in "sync aggregates"

Added by okurz 4 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
Start date:
2023-07-31
Due date:
% Done:

0%

Estimated time:

Description

Observation

https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs/1717996 says on top, before the log:

There has been a timeout failure or the job got stuck. Check your timeout limits or try again

and the end of the log:

…
2023-07-28 09:42:54 INFO     Ignoring job '11674961' in development group 'Test Security'
2023-07-28 09:42:54 INFO     Ignoring job '11674962' in development group 'Test Security'
2023-07-28 09:42:54 INFO     Ignoring job '11676644' in development group 'Test Security'
2023-07-28 09:42:54 INFO     Ignoring job '11677189' in development group 'Test Security'

so likely the script execution ./qem-bot/bot-ng.py -c /etc/openqabot --token [MASKED] aggr-sync-results really got stuck. Unfortunately it seems we also don't have any log files uploaded as artifacts. Maybe we can add another layer around the command still within the gitlab CI shell session with the timeout command so that we abort before gitlab CI aborts us and maybe then we can still upload artifacts?

Workaround

Retrigger job in gitlab CI

No data to display

Actions

Also available in: Atom PDF