On Qua, 2016-03-23 at 21:06 +0800, Ting-Wei Lan wrote:
I am sorry for causing problems. I have modified my script to reduce
the build frequency from 4 times a day to 1 time a week for ppc64le.
seems that ppc64le builders are not able to process builds as fast as
x86_64 and i386 builders, and they usually hang for days.
I don't know what to say, sorry for my bad mood, sometimes is a way to
write things quickly, but be rewarded feels good.
Thanks for reply and explaining what happened.
Anyway, to be clear, I don't expect all ppc64le problems be solved but
it will help. Builders, now, are running very well ...
> I don't understand the goal , but if last
> build doesn't finish , shouldn't start another one ... ,
As vim upstream releases updates much faster than before, I no longer
manually submit builds for lantw44/vim-latest. These builds are
automatically submitted by my crontab every 6 hours when an update is
found. My script doesn't check whether the old build is finished
submitting a new build, and it hardly causes problems for x86_64 and
i386 because these builds usually finish in 10 minutes.
I use 'copr-cli build -r' separate ppc64le builds and non-ppc64le
builds now. Non-ppc64le builds are still submitted when new updates
released, but ppc64le builds are only submitted once a week. I hope
is much less possible for my lantw44/vim-latest builds to block other
Looks a good idea (submit builds automatically :) ) , you could, easily
, watch the page https://copr.fedorainfracloud.org/status/waiting/ and
with a web scraper, see if you have running jobs and if you have, you
may delay the next update ...
Web scraper example:
-qO - | grep lantw44/vim-latest
Sérgio M. B.