I happened to be watching the screen during a recent piglit run and saw a stacktrace fly by. However, when the test run completed, I did not have any "crashes" in my summary. It turns out that the crash was during the "spec/!OpenGL 1.0/gl-1.0-beginend-coverage/glPixelMapfv" - the glPixelMapfv subtest of gl-1.0-beginend-coverage. The crash terminated gl-1.0-beginend-coverage. However piglit processes each (completed) subtest as a separate test. Each of the subtests that passed gets the result "pass", with their own identical 'info', 'command', 'time', 'subtest' and 'returncode' fields. Note that the "returncode" field in this case is -6 for all of them (all of the passing subtests), since the master test process crashed. However, there is no separate test item for the master test, to mark the "crash" result. Similarly, since piglit really has no way of knowing how many subtests the master test should run, it doesn't even know which subtest crashed, nor which subtests didn't even get run.
938ec48e2575b78defd06d169f704ed8d4f11bce logs a subtest named 'unknown' with result crashed if a test with subtests crashes. Since the name of the crashing subtest still isn't recorded and subsequent subests aren't logged as not-run, I'm leaving this bug open for now.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/piglit/issues/1.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.