I am just sending more than 70 000 tasks to production instance of Copr. Why? Because of: http://miroslav.suchy.cz/blog/archives/2016/04/21/wip_rebuilding_all_pypi_mo... I'm throttling the speed and I am sending one task each 15 seconds. So it will take 12 days before I sent everything. On the other hand there should be no long queue. If you will see some long queue in "Waiting" despite my throttling, then I would like to emphasise that every user (including me) can have only 6 concurent tasks. And we can have up to 25 builders in parallel. So there is still 19 builders always available to process task of other users, so your task should be build as fast as usually.
Of course there can be some bug. So if you think that something bad happened then please contact me.
On Friday 06 of May 2016 14:22:28 Miroslav Suchý wrote:
I am just sending more than 70 000 tasks to production instance of Copr. Why? Because of: http://miroslav.suchy.cz/blog/archives/2016/04/21/wip_rebuilding_all_pypi_mo... I'm throttling the speed and I am sending one task each 15 seconds. So it will take 12 days before I sent everything. On the other hand there should be no long queue. If you will see some long queue in "Waiting" despite my throttling, then I would like to emphasise that every user (including me) can have only 6 concurent tasks. And we can have up to 25 builders in parallel. So there is still 19 builders always available to process task of other users, so your task should be build as fast as usually.
Is this still truth even for the rubygem batch? Seems like the ruby builds have some higher priority (waiting about ~2 hours before some other build gets processed).
Pavel
Dne 7.6.2016 v 11:26 Pavel Raiskup napsal(a):
Is this still truth even for the rubygem batch? Seems like the ruby builds have some higher priority (waiting about ~2 hours before some other build gets processed).
Ops. One config value got lost during latest upgrade. Should be fixed now.
Mirek
On 7 Jun 2016, at 12:25, Miroslav Suchy msuchy@redhat.com wrote:
Dne 7.6.2016 v 11:26 Pavel Raiskup napsal(a):
Is this still truth even for the rubygem batch? Seems like the ruby builds have some higher priority (waiting about ~2 hours before some other build gets processed).
Ops. One config value got lost during latest upgrade. Should be fixed now.
Mirek
Not sure if something similar happening again. Seeing only @rubygems tasks running at the moment and nothing else. Maybe serves me right for only needing it on everyone’s relaxing weekend! I’ll wait, be great if someone could check this is normal though #hugops :)
Thanks
copr-devel@lists.stg.fedorahosted.org