On Wed, 19 Feb 2025 at 15:00, Alex Bennée <alex.ben...@linaro.org> wrote: > > Hi, > > As I was looking at the native context patches I realised our existing > GPU testing is a little sparse. I took the opportunity to split the > test from the main virt test and then extend it to exercise the 3 > current display modes (virgl, virgl+blobs, vulkan). > > I've added some additional validation to ensure we have the devices we > expect before we start. It doesn't currently address the reported > clang issues but hopefully it will help narrow down what fails and > what works. > > Once I've built some new buildroot images I'll re-spin with a while > bunch of additional test binaries available.
Running on a non-sanitizer debug build, I found that aarch64_virt_with_virgl_gpu hit the timeout. Looking at the output the last thing printed is 2025-02-20 11:46:36,864: [shadow] <default>: FPS: 45 FrameTime: 22.585 ms That timestamp is 4 minutes into the test run, and the same [shadow] test takes over 2 minutes on the with_virgil_blobs_gpu test, so it looks like it just hit the 360s timeout and might well have finished OK if it had been allowed to keep running. Actually I'm surprised the other one didn't hit a timeout, because its log timestamps show it running from 11:35:03,896 to 11:42:26,468 which is definitely more than 360s. Is there a less time-intensive test of the virgl code we can use? check-functional already has way too many tests that take minutes to run... -- PMM
