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
0001-Implement-dmesg-monitored-option.patch
Description: Binary data
_______________________________________________ Piglit mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/piglit
