Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Admin message
The migration is almost done, at least the rest should happen in the background. There are still a few technical difference between the old cluster and the new ones, and they are summarized in this issue. Please pay attention to the TL:DR at the end of the comment.
Starting dynamic subtest: bcs0[455.785555] Per-test timeout exceeded. Killing the current test with SIGQUIT.[575.751864] Timeout. Killing the current test with SIGKILL.[575.848561] Closing watchdogs[575.855026] Initializing watchdogs[575.855198] /dev/watchdog0
Edited
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
A CI Bug Log filter associated to this bug has been updated by Lakshmi Vudum:
Description: BXT: igt@gFem_ctx_persisw tence@engines-mixed@bcts0 - timeout - Received signal SIGQUIT.
Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND (machine_name IS IN ["fi-bxt-dsi", "fi-bxt-j4205"] OR machine_tag IS IN ["BXT"]) AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@kms_plane_cursor@pipe-a-primary-size-64", "igt@gem_ctx_persistence@engines-mixed@bcs0"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["timeout"])) AND stderr ~= 'Received signal SIGQUIT.'
LAKSHMINARAYANA VUDUMchanged title from igt@gem_ctx_persistence@engines-mixed@bcs0 - timeout - Received signal SIGQUIT, slow test to igt@gem_ctx_persistence@engines-mixed@bcs0 - timeout - Received signal SIGQUIT, slow test (drmtip_467)
changed title from igt@gem_ctx_persistence@engines-mixed@bcs0 - timeout - Received signal SIGQUIT, slow test to igt@gem_ctx_persistence@engines-mixed@bcs0 - timeout - Received signal SIGQUIT, slow test (drmtip_467)