You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Back trace present after the usual ------------[ cut here ]------------
Seems to be random.
At a quick glance, looks like a race condition with rt-kernel and systemd-udevd: BUG: scheduling while atomic: systemd-udevd/651/0x00000003
Triggering another backtrace: WARNING: CPU: 12 PID: 651 at kernel/sched/core.c:5781 preempt_count_sub+0x5e/0xa0
The test "SEAPATH-00080 - no backtraces" randomly failed and block the
CI.
This commit allow the CI to pass even if this test fails.
The test will still be integrated in the test report and a warning will
be displayed in the CI logs.
An issue is open for this bug on the ansible repo :
seapath/ansible#164
Signed-off-by: Erwann Roussy <erwann.roussy@savoirfairelinux.com>
eroussy
added a commit
to seapath/ci
that referenced
this issue
Mar 20, 2023
The test "SEAPATH-00080 - no backtraces" randomly failed and block the
CI.
This commit allow the CI to pass even if this test fails.
The test will still be integrated in the test report and a warning will
be displayed in the CI logs.
An issue is open for this bug on the ansible repo :
seapath/ansible#164
Signed-off-by: Erwann Roussy <erwann.roussy@savoirfairelinux.com>
backtrace test didn't pass on virtu3 (SEAPATH-0080)
dump_dmesg.txt
The text was updated successfully, but these errors were encountered: