On Tue, May 16, 2017 at 07:42:51AM +0000, Lofstedt, Marta wrote: > I hereby pull-out this patch. > The idea of it was to know if we were already wedged at the beginning of testing, that would give us information on how to interpret silly results; such that test starting to get skipped and/or we got dmesg-warns/incomplete on tests that usually should be skipped. > Also, we are planning to soon deploy a piglit.conf solution where testing will be terminated on wedged, so I agree that my test isn't really needed. Not everything is broken by wedged; internally we just use that as an indicator that GEM is hosed. KMS should still work, we must still be able to drive the displays to show the error and keep the servers alive until the data is saved (and hopefully gracefully degrade that we don't have to interrupt their immediate session). Whilst that may be out of scope for BAT, it should not be completely beyond us for robustness testing. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
