mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-05-18 22:28:06 +02:00
3c0e4be89b
it's been flaking with "2022-05-05 16:29:49.055151: [0m[31mERROR - Failure getting run results: parsing results: Reading from dEQP: timed out waiting for fd to be ready (See \"//results/c32.r1.log\")" and a pile of missings since the brief "whoops, HW CI failed to listen to the test exit code" regression. The only ways I know of to hit this case would be: 1) The deqp binary abruptly wedges on its own. This happens with NFS failures sometimes, but the rest of the run went fine and we never got the kernel complaining about NFS, so that seems unlikely. 2) The stderr pipe filled up before stdout was completed, and deqp got wedged trying to output stderr (happens sometimes when you do like NIR_DEBUG=print in your run). Both of these seem unlikely, given that we've got a big .qpa file that made it all the way to writing out test case durations at the end of the run before abruptly terminating. Why didn't we have at least some of the test results parsed? The next deqp-runner release we integrate will solve #2, and cleans up these error paths a bunch, so I'm hoping we get more information soon. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16350> |
||
|---|---|---|
| .. | ||
| amd | ||
| android_stub | ||
| asahi | ||
| broadcom | ||
| compiler | ||
| drm-shim | ||
| egl | ||
| etnaviv | ||
| freedreno | ||
| gallium | ||
| gbm | ||
| getopt | ||
| glx | ||
| gtest | ||
| hgl | ||
| imagination | ||
| imgui | ||
| intel | ||
| loader | ||
| mapi | ||
| mesa | ||
| microsoft | ||
| nouveau | ||
| panfrost | ||
| tool | ||
| util | ||
| virtio | ||
| vulkan | ||
| meson.build | ||