[Piglit] ctrl-c behaviour

Dave Airlie airlied at gmail.com
Thu Feb 10 19:06:48 PST 2011

So it used to be that I'd start a piglit run, and when one tripped
over the GPU and it had to reset, I'd hit ctrl-c and it would move
onto he next test and my test run would complete and I'd get a decent
log, now when I hit Ctrl-C it kills the test run.

Any way we can the old behaviour back or at least an option for it?


More information about the Piglit mailing list