Hi, Over the last couple of months, a couple of contributors have been working on enabling openQA for aarch64, and the current state looks good enough for a start. To learn more about openQA , visit http://os-autoinst.github.io/openQA/ (there is also openqa.org which is however completely unrelated). So far, publishing and testing of Tumbleweed for ARM (aarch64) was happening completely independent. It is however better if the automated testing result is used to decide whether or not the current snapshot will be published to end users.
As recently of bigger changes have entered tumbleweed (https://news.opensuse.org/2016/02/10/systemd-updates-ambitious-yast-changes-in-tumbleweed/), it seems now is a good timing to switch to a tested publishing method. This means from now on openQA will test the snapshot first in a staging area, and only if it passes the defined testing criteria the snapshot will be published. So far, snapshots were published and only afterwards tested. Since publishing happened via the build service, which due to the recent upgrades is significantly bottlenecked and took several days or more, we have enough time to test the snapshot (which does not have to be published right away) and then decide on whether or not to publish the current tree without significant drawbacks. Therefore, publishing happens from now on not directly anymore but only via openQA. As the current state is failing the testing, it is actually a good thing as we'll be ironing out the issues and then have a stable snapshot (including images) published. That however also means there will likely not be a snapshot update for the next few days as we'll work out kinks and issues. Please note that armv6/v7hl is currently not covered by openQA and hence is published like before. However I started a bit on enabling testing of armv7 as well, but that will take a bit more time until we can make the switch. Greetings, Dirk -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
