[Piglit] [Bug 94741] piglit fails to determine deadlock happened during i-g-t test

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Mar 30 17:50:24 UTC 2016


Dylan Baker <baker.dylan.c at gmail.com> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|---                         |NOTOURBUG

--- Comment #9 from Dylan Baker <baker.dylan.c at gmail.com> ---
It's doing exactly what it's intended to do when it doesn't change the result
to dmesg-*. Basically what happens is after the test runs and it does it's own
test specific result handling (the interpret_result method) it gets passed to
the Dmesg class which will change pass to dmesg-warn, and warn and fail to
dmesg-fail. You can look at the code in dmesg.py (BaseDmesg.update_result). So
skip shouldn't be converted, piglit assumes that the test code knows what it's
doing when it sets the status to skip.

I think that we've resolved this isn't a piglit bug, it's an IGT bug. So I'm
going to mark this resolved as 'notourbug', but please reopen if that's not

You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/piglit/attachments/20160330/c408747c/attachment.html>

More information about the Piglit mailing list