On Wed, Jul 31, 2019 at 04:35:11PM +0100, Tom Hughes wrote:
On 31/07/2019 16:10, Pierre-Yves Chibon wrote:
>On Wed, Jul 31, 2019 at 03:15:32PM +0100, Richard W.M. Jones wrote:
>>On Tue, Jul 30, 2019 at 11:11:34AM -0700, Kevin Fenzi wrote:
>>>In this case it's koji.
>>>
>>>For every package in the mass rebuild (f31-pending tag) robosign asks
>>>koji "hey, is foobar-1.0.1-1.fc31 signed' ? koji checks...
"yes, it is".
>>>robosign: "great, then I ask you to write out the signed rpms now"
>>>koji: "ok, writing them out to disk again"
>>>
>>>it's mostly this last step thats slow. I am not sure if koji is just
>>>seeing if they were written out and returning, or actually re-writing
>>>them out. It seems like it might be the latter, which makes me suspect
>>>koji could optimize this somewhat.
>>
>>It's still taking a long time today to get builds through Koji and
>>into Rawhide. Is there a reason we need to sign builds in Rawhide?
>
>My canary took 14 minutes this morning, so that's within the usual time for it.
>
>I'll run it again right to see if it is slower now.
It seems to vary quite a bit. So far today I've seen about 45 minutes
then 15 and I'm now waiting on another one that's at 50 minutes and
counting.
I've been waiting so far nearly 2 hours for this one to get into the
buildroot:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1344542
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
Read my programming and virtualization blog:
http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top