radv/ci: reboot the DUTs when hitting a ring timeout
I am not super happy about doing this, as this means we will potentially be introducing regressions because CI would have papered over a rare race condition... But the situation is that this is already happening, and improving the reliability will likely come from tracking the occurence rate of hangs in an external system. Signed-off-by: Martin Roukala (né Peres) <martin.roukala@mupuf.org> Acked-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16472>
This commit is contained in:
parent
1542ab70eb
commit
815d192c7b
|
@ -198,7 +198,7 @@
|
|||
B2C_LOG_LEVEL: 6
|
||||
B2C_POWEROFF_DELAY: 15
|
||||
B2C_SESSION_END_REGEX: '^.*It''s now safe to turn off your computer\r$'
|
||||
B2C_SESSION_REBOOT_REGEX: 'GPU hang detected!'
|
||||
B2C_SESSION_REBOOT_REGEX: '(GPU hang detected!|\*ERROR\* ring [^\s]+ timeout|The CS has been cancelled because the context is lost)'
|
||||
B2C_TIMEOUT_BOOT_MINUTES: 240
|
||||
B2C_TIMEOUT_BOOT_RETRIES: 2
|
||||
B2C_TIMEOUT_FIRST_MINUTES: 5
|
||||
|
|
Loading…
Reference in New Issue