Hello there, fellow Ubuntu developers!
There has been some work recently on enabling the riscv64 architecture for automated testing. Things are now running quite smootly, but please take good note of the following:
- The virtual machines, just like the Launchpad builders, are running in emulation. That means testing time will be much slower than for other architectures.
- To cope with that, every timeout that you might be used to (normal or long tests) have been multiplied by 4 by default for this architecture.
- The number of workers right now is 96, similar to most other architectures. That means you can still expect quite a high level of parallelization when processing the queue.
- The intent is absolutely not to block
-proposedmigrations on this architecture right now, mainly because of the slowness, and lack of feedback. That will however likely become the case in the not too close future, when things have stabilized, and we get real hardware to run the tests on. - Only Jammy, Noble, Oracular, and Plucky are working. While Focal
riscv64is kind of enabled on Launchpad, the infrastructure will never be able to test that combination. - To exercise the architecture, we have had Britney queue tests, only for Noble and onward, for the packages in
main, but will consider them automaticallyforce-badtest, so as not to block on the test result (Thanks @juliank for the MP, and @paride for all the subsequent debugging sessions!). That doesn’t prevent you from manually running tests on Jammy or for packages inuniverse.
We’ll be looking for feedback on how this architecture behaves, and obviously the goal is to get that on par with all the other architectures. If you see a test failing for a package only on this architecure, please open a bug against auto-package-testing, and ping qa-help on #devel:ubuntu.com to let us know.
Happy bug hunting!