On Fri, Sep 20, 2019 at 11:41 AM Kevin Fenzi <kevin@xxxxxxxxx> wrote:
On 9/20/19 6:07 AM, Kaleb Keithley wrote:
> On Thu, Sep 19, 2019 at 7:33 PM Kaleb Keithley <kkeithle@xxxxxxxxxx> wrote:
>
>> On Thu, Sep 19, 2019 at 2:18 PM Kevin Fenzi <kevin@xxxxxxxxx> wrote:
>>
>>> On 9/19/19 5:26 AM, Kaleb Keithley wrote:
>>>> Someone with privs please kick it. Thanks
>>>>
>>>> https://bodhi.fedoraproject.org/updates/FEDORA-2019-995f3ae953
>>>
>>> Done. Do note that you can do this too, just untag it from f32-pending
>>> and tag it again into f32-pending.
>>
>>
> Question: you did it. I did it. In Koji[1] it has f32 and
> f32-updates-candidate tags. And in bodhi[2] it's still showing as pending
> testing. What should it be? What should I do at this point to get it out of
> pending testing and into testing?
There is no testing for rawhide.
The f32 tag means it should be in composes.
The issue here is that you created this bodhi update... for rawhide
gating it just does all the work, you should not create updates for
rawhide.
I can see if I can get someone to poke it and make it reflect reality,
but it's already stable and there's nothing further to do (except clean
up what bodhi thinks).
Okay. Other builds I've done for f32 (gluster, nfs-ganesha, earlier ceph builds even) all went straight to stable in bodhi, but this one didn't, despite waiting several hours.
Then there's the ceph build for f31[1] that's still stuck in pending testing after two days.
And the ceph build for f30[2] that's been in testing for 15 days that isn't allowing me push it to stable.
???
Thanks for your help though, greatly appreciated.
Regards,
--
Kaleb
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
