Hi Freek, Am 22.01.2018 um 12:08 schrieb Freek de Kruijf: > I filed a bug report with this subject as: > https://bugzilla.opensuse.org/show_bug.cgi?id=1077011
I don't see how that will help, as a Bugzilla ticket is only really useful when it can be assigned to someone to work on it and be closed at some point. "is not kept up-to-date" doesn't quite tick that box for me. That openQA sometimes does not pass happens for x86 too, just not that often, and they get more frequent snapshot builds to test so that they're not blocked as long. We already got a donation of two servers a few months back to help shorten that build cycle. > I am using the image for the Raspberry Pi 3, which is available via OBS and > which is build using the newest packages also available in OBS. This image > should be available in the regular repository, also mentioned in the wiki. > Also the newest packages should be available via the repository zypper uses > to > upgrade Tumbleweed, which is currently not the case. Fully agree that that is the ideal case - however note that there's a difference between "snapshot" and "standard" repository on x86, too, with snapshot corresponding to what's published and standard being the very latest. > Can I be of any help with this? Yes! :) The openQA build results need to be monitored, and if there are failures they need to be looked at and acted upon. It won't help to file 15 bugs for 15 test failures when the problem is really the openQA worker, but occasionally there were package dependency issues, surfacing as warning/error messages in the screenshots before a failure. The builds that were fully reviewed show a grey star next to the date, and if you click on that build it will show a blue bug symbol next to the failing test cases. https://openqa.opensuse.org/group_overview/3 There are no notifications of when a new build has been tested, and Dirk and I have been looking at the test results as time permits. Any help 1) bringing new failing builds to our common attention and 2) investigating what may be going wrong to ultimately 3) get the failures annotated with bugs that either need to be fixed before publishing or can be ignored by ttm for the next build would be appreciated. And obviously where packages are failing to build (113 for aarch64 atm), some may be a generic issue also found in openSUSE:Factory for x86_64, some may be an intermittent worker problem, and some others an actual ARM-specific problem that Dominique and the maintainers are simply not seeing on x86. So if a package you care about has failing dependencies, then Submit Requests in OBS to get those builds fixed properly may be a solution for certain openQA and repo publishing problems. https://build.opensuse.org/project/show/openSUSE:Factory:ARM https://build.opensuse.org/project/monitor/openSUSE:Factory:ARM?arch_aarch64=1&defaults=0&failed=1&repo_standard=1 Cheers, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
