Hey Adam, Sorry for the delayed reply here. I wanted to reply properly, then it got lost in my inbox. > Hey folks! Just a heads up that I merged a branch I've had lying around > for weeks that enables *some* of the openQA desktop tests on the > aarch64 Workstation image. Thanks for this, it's really awesome! > I left out some with known issues. desktop_notifications_postinstall > needs to boot to runlevel 3, which is actually a bit tricky because of > UEFI - we don't get the boot menu with a usable timeout and the trick > we use to work around that on x86_64 (where we run the tests on BIOS) > doesn't work on UEFI because the setting is in the UEFI vars which are > not part of the main disk image. Can you use "efibootmgr --timeout XX" to set a usable timeout at some point during the process? > To fix this I think I need to have the 'image deploy' test upload its > UEFI vars disk image and have the desktop_notifications_postinstall > test attach that as well as the main disk image, but I need to look > into the ins and outs of that a bit and this is my last work day of the > year, so I'll do it next year. > > The desktop_login test is generally fragile (things tending to get > stuck or time out), but if it gets that far, it *always* fails when it > tests locking the screen; on aarch64 this seems to cause the VM to > permanently stop updating the display, or something. Again I haven't > had time to look into this, and I want to enable the other tests > without waiting for it. Huh, weird, I would have thought given it's basically the same driver stack it would have been closest here. > The desktop_browser test is also failing, but I left that in because > it's not a test bug, it's a distro bug. Firefox builds have just been > disabled on aarch64 since 2020-11-20, so current composes don't have > Firefox in them on aarch64 at all. There's a bug related to this: > https://bugzilla.redhat.com/show_bug.cgi?id=1897675 > which I just gave a bit of a bump, because it shouldn't really be > acceptable to just turn off our default browser's build on one of our > primary arches for weeks at a time :( That's been an ongoing issue with the firefox maintenance for years sadly :( > This also breaks several of the other tests which use Firefox, like the > Cockpit and FreeIPA browser tests. > > The tests should run on openQA prod from the next compose. The branch > has been deployed on openQA lab (staging) for weeks (including the > broken tests), so you can see how it's been behaving there. How are they generally after a few weeks running? Peter _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
