| Summary: | selftest fedora test_testimage_virgl_gtk_sdl failure | ||
|---|---|---|---|
| Product: | [QA/Testing] Runtime Testing | Reporter: | Richard Purdie <richard.purdie> |
| Component: | testimage | Assignee: | Alexander Kanavin <alex.kanavin> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | randy.macleod |
| Version: | unspecified | ||
| Target Milestone: | 3.1 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Richard Purdie
2020-03-10 21:59:17 UTC
This is a strange one, and I'm not sure how to proceed or reproduce. The virgl runtime test first check the kernel messages for sanity, then runs kmscube: http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/tree/meta-selftest/lib/oeqa/runtime/cases/virgl.py For some reason, mesa fell back to software renderer, instead of virgl. The same test passed fine on ubuntu, debian, or in fact, also in fedora in subsequent master-next a-full run. Let's observe if this happens again and try to narrow down the circumstances. So this hasn't been seen again in a month? I guess it's a WORKSFORME :-/ |