On Tue, Jan 23, 2018 at 02:21:02PM +0100, Adam Williamson wrote: > On Tue, 2018-01-23 at 10:32 +0100, Pierre-Yves Chibon wrote: > > > > We just sent an announcement about this, sorry for being late on this. > > > > Basically, you can "waive" test results using waiverdb-cli (dnf install > > waiverdb-cli) which will allow the update to go through despite of the failing > > test. > > We're working on putting this into bodhi itself for easier use. > > Note, just waiving this kind of failure one-by-one doesn't seem like > the proper fix for this to me. Patrick told me yesterday that he'd seen > or been told about a different (I think) but similar case; I think > there may be kind of a generic issue with the ABI diff test checking > the ABI of shared objects that aren't actually 'public' in any > meaningful way. We should look at that as a generic issue. I'm sending > a mail to qa-devel@ to flag this up to the Taskotron devs. We could > consider dropping this test from the gating list again until this is > looked into... I've removed the abicheck requirement from the greenwave policies for now until we know more: https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=465f155d140a9fbe34f0f51dbfc2137b2900a6f8
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
