Message ID | 20220715155859.665686-1-richard.purdie@linuxfoundation.org |
---|---|
State | New |
Headers | show |
Series | selftest/runtime_test/virgl: Disable for all almalinux | expand |
On Fri, 15 Jul 2022 at 17:59, Richard Purdie <richard.purdie@linuxfoundation.org> wrote: > - if distro and distro in ['debian-9', 'debian-10', 'centos-7', 'centos-8', 'ubuntu-16.04', 'ubuntu-18.04', 'almalinux-8.5', 'almalinux-8.6']: > + if distro and (distro in ['debian-9', 'debian-10', 'centos-7', 'centos-8', 'ubuntu-16.04', 'ubuntu-18.04'] or distro.startswith('almalinux')): I guess almalinux-9 has also shown the same problem as 8? Should this be 'or distro.startswith('almalinux-8') or distro.startswith('almalinux-9') rather? It will be a while before 10 is available , and that should be evaluated on its own. Alex
On Fri, 2022-07-15 at 18:13 +0200, Alexander Kanavin wrote: > On Fri, 15 Jul 2022 at 17:59, Richard Purdie > <richard.purdie@linuxfoundation.org> wrote: > > - if distro and distro in ['debian-9', 'debian-10', 'centos-7', 'centos-8', 'ubuntu-16.04', 'ubuntu-18.04', 'almalinux-8.5', 'almalinux-8.6']: > > + if distro and (distro in ['debian-9', 'debian-10', 'centos-7', 'centos-8', 'ubuntu-16.04', 'ubuntu-18.04'] or distro.startswith('almalinux')): > > I guess almalinux-9 has also shown the same problem as 8? Should this > be 'or distro.startswith('almalinux-8') or > distro.startswith('almalinux-9') rather? It will be a while before 10 > is available , and that should be evaluated on its own. Michael basically said that we were unlikely ever to get vgem working with Alma. It was almalinux-9 that I was adding but I think we wait and evaluate the situation with 10 and then someone can send a patch if we can add it. Cheers, Richard
On Fri, 15 Jul 2022 at 22:42, Richard Purdie <richard.purdie@linuxfoundation.org> wrote: > Michael basically said that we were unlikely ever to get vgem working > with Alma. It was almalinux-9 that I was adding but I think we wait and > evaluate the situation with 10 and then someone can send a patch if we > can add it. Michael, can you share the findings please? Is 10 and beyond unlikely to fix this for some reason? (from what I remember the problem is lack of vgem module in any of the rhel/alma distro packages, which strangely is not a problem with fedora) Alex
diff --git a/meta/lib/oeqa/selftest/cases/runtime_test.py b/meta/lib/oeqa/selftest/cases/runtime_test.py index 8eacde40adb..857737f730c 100644 --- a/meta/lib/oeqa/selftest/cases/runtime_test.py +++ b/meta/lib/oeqa/selftest/cases/runtime_test.py @@ -252,7 +252,7 @@ class TestImage(OESelftestTestCase): import subprocess, os distro = oe.lsb.distro_identifier() - if distro and distro in ['debian-9', 'debian-10', 'centos-7', 'centos-8', 'ubuntu-16.04', 'ubuntu-18.04', 'almalinux-8.5', 'almalinux-8.6']: + if distro and (distro in ['debian-9', 'debian-10', 'centos-7', 'centos-8', 'ubuntu-16.04', 'ubuntu-18.04'] or distro.startswith('almalinux')): self.skipTest('virgl headless cannot be tested with %s' %(distro)) render_hint = """If /dev/dri/renderD* is absent due to lack of suitable GPU, 'modprobe vgem' will create one suitable for mesa llvmpipe software renderer."""
We can't support vgem on RHEL derived distros so disable this test for all almalinux hosts rather than specific versions. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> --- meta/lib/oeqa/selftest/cases/runtime_test.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)