[Piglit] [PATCH][RFC] Add dmesg option for reboot policy
yann.argotti at linux.intel.com
yann.argotti at linux.intel.com
Mon Nov 2 06:57:51 PST 2015
This adds a policy which advises when user should reboot system to avoid
noisy test results due to system becoming unstable, for instance, and
therefore continues testing successfully.
To do this, a new Dmesg class is proposed which is not filtering dmesg and
monitors whether or not one of the following event occurs:
- gpu reset failed (not just gpu reset happened, that happens way too
often and many tests even provoke hangs intentionally)
- gpu crash,
- Oops:
- BUG
- lockdep splat that causes the locking validator to get disabled
If one of these issues happen, piglit test execution is stopped
-terminating test thread pool- and exit with code 3 to inform that reboot
is advised.
Then test execution resume, after rebooting system or not, is done like
usually with command line parameter "resume".
To call it, use command line parameter: --dmesg monitored
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Implement-dmesg-monitored-option.patch
Type: application/octet-stream
Size: 13885 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/piglit/attachments/20151102/f636b8f5/attachment-0001.obj>
More information about the Piglit
mailing list