I failed to reproduce it after running live_hangcheck in a loop for couple hours. And the same preceded with live_contexts just in case.
The failure is so far localized to one particular machine and happened two times only? Given this should we move the priority down from highest?
What I did hit *once* in all these run is probably a rather worrying "ring head not parked" error.
Seen according ti cibuglog on
(In reply to Jani Saarinen from comment #2)
> Seen according ti cibuglog on
iommu / guc are unrelated bugs.
There is simply no information here to do any diagnosis. ReadyForDev not.
Last seen 1 week, 3 days / 145 runs ago
Used to happen several time a day, now hasn't happened for 12 days. I think we should close it.
igt@drv_selftest@* are not run, so no results.
Tvrtko, any idea why these tests are not run? Are these tests are not supposed to run? If so, I can close this bug.
(In reply to Lakshmi from comment #6)
> igt@drv_selftest@* are not run, so no results.
> Tvrtko, any idea why these tests are not run? Are these tests are not
> supposed to run? If so, I can close this bug.
they got renamed to igt@i915_selftest@ ;)
So how do we track this in CI bug logger? I still see no failure related to this bug and I have no idea how to look for the same failure in the renamed tests.
(In reply to Francesco Balestrieri from comment #8)
> So how do we track this in CI bug logger? I still see no failure related to
> this bug and I have no idea how to look for the same failure in the renamed
Francesco, filter has been updated according to the new name in CI bug log. So, its the same bug in CI bug log where you can look at failures with the new name.