On Thu, 2018-12-06 at 15:25 +0000, Fedora compose checker wrote: > No missing expected images. > > Compose FAILS proposed Rawhide gating check! > 5 of 47 required tests failed > openQA tests matching unsatisfied gating requirements shown with **GATING** below So - this is a new feature of check-compose I wrote yesterday :) As part of the 'NoMoreAlpha' change from a few releases back: https://fedoraproject.org/wiki/Changes/NoMoreAlpha we planned to start gating Rawhide composes - only syncing them out to become the current public state of the 'Rawhide' tree if they pass some subset of the automated compose tests. However, this has not yet been implemented. An initial gating policy was actually committed to the Fedora Greenwave config some months back by Ralph Bean, and since then it's been possible to ask Greenwave whether a given compose passes or fails the policy - but nothing was hooked up beyond that; no-one's been doing anything with that information. Ultimately the idea is that the Greenwave decision should be hooked into the compose sync process, but I thought before we go that far, it'd be useful to know just how often composes actually *do* meet the requirements. So I enhanced check-compose to request the decision from Greenwave and include it in the output, like this. This should help us get an idea just how often we'd be refusing to sync composes if we turned gating on. The failures that fail the gating check today are down to https://bugzilla.redhat.com/show_bug.cgi?id=1654537 and the Everything netinst tests for both x86_64 and UEFI failing because of the network not being up in the guest for some reason. The FreeIPA bug I'm hopeful we can get fixed soon, I'm not sure what's going on with the netinst failure, I'll have to look into that. (It's a bit tricky because, when the network in the guest doesn't work, we don't get any logs from the test...) Eagle-eyed readers may not a slight bug in the new feature: Greenwave reports *5* failed requirements, but the details below show only *4* tests with **GATING**. This is because the other failed test - the FreeIPA server test - doesn't show up in the check-compose output for some reason. If you re-run check-compose now, it *does* show up, so this is likely some kind of ordering issue to do with exactly what state that job is in when check-compose runs (my working theory is that it's in 'uploading' state - that could cause it to fall between some code cracks). I'll see if I can fix that. Thanks folks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
