QA (public) » openQA Project (public) » openQA Tests (public)

From the https://openqa.suse.de/tests/16460705/logfile?filename=autoinst-log.txt

[2025-01-15T17:49:17.848165Z] [debug] [pid:6790] tests/wicked/locks_init.pm:28 called lockapi::mutex_wait
[2025-01-15T17:49:17.848467Z] [debug] [pid:6790] <<< testapi::record_info(title="Paused", output="Wait for wicked_barriers_created (on parent job)", result="ok")
[2025-01-15T17:49:17.849652Z] [debug] [pid:6790] mutex lock 'wicked_barriers_created'
[2025-01-15T17:49:17.878949Z] [debug] [pid:6790] mutex lock 'wicked_barriers_created' unavailable, sleeping 5 seconds

When looking at the dependencies of that job, namely https://openqa.suse.de/tests/16460702, we can see that job is cancelled (so it never reached the mutex and hence the other job time-outed).

I believe this is an issue we already know from #174583, the second example

{"blocked_by_id":null,"id":16374878,"result":"skipped","state":"cancelled"}
{"blocked_by_id":null,"id":16374879,"result":"timeout_exceeded","state":"done"}

Looking at the last job, it has already passed, so I believe the issue is actually about the proper cancellation / correct restarts of the whole dependent jobs.

I propose to block on #174583 where we might improve this behavior.

seems to be an upstream openQA issue in the scheduler, possibly fixed by https://github.com/os-autoinst/openQA/pull/6130. History of jobs like from https://openqa.suse.de/tests/latest?arch=aarch64&distri=sle&flavor=Online&machine=aarch64&test=wicked_basic_sut&version=15-SP7#next_previous like passed and stable. Assuming fixed