On Mon, 2018-03-26 at 12:14 -0400, Ralph Bean wrote:
> On Mon, Mar 26, 2018 at 08:53:41AM -0500, Michael Cronenworth wrote:
> > I have attempted to create waivers for two updates, but they are still
> > unable to be pushed. What have I done wrong?
> > 
> > https://bodhi.fedoraproject.org/updates/FEDORA-2018-c5a0e704d6
> > https://bodhi.fedoraproject.org/updates/FEDORA-2018-ec1108333e
> > 
> > $ waiverdb-cli -t dist.rpmdeplint -s '{"item": "wine-3.4-1.fc28", "type":
> > "koji_build"}' -p "fedora-28" -c "This is fine"
> > Created waiver 94 for result with subject {"item": "wine-3.4-1.fc28",
> > "type": "koji_build"} and testcase dist.rpmdeplint
> 
> It looks like you did the right thing to me.
> 
> IIRC, Bodhi checks back with Greenwave once every 6 hours, so you'll
> have to wait for that window to close for Bodhi to notice the change.
> (The plan is to have Bodhi listen to Greenwave's bus messages which
> would eliminate wait period like this.

FWIW I think I had the same problem; I tried to submit waivers for some
rpmdeplint failures in the OpenCV 3.4.1 rebuild update and they never
seemed to 'take' (even after more than 6 hours). In the end I just
unpushed and repushed the update to get the tests re-run.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Reply via email to