What does 'Copr timeout => sending INT' mean in builder-live.log? This problem has existed for a long time and it often shows in my Chromium builds. While it is possible to click 'Resubmit' on failed builds and it usually takes 1 or 2 rebuilds to get successful builds, having to do the same thing for each Chromium update takes a lot of time because each build usually takes more than 15 hours.
Here is an example file. Note that the file is large (> 600 M). https://copr-be.cloud.fedoraproject.org/results/lantw44/chromium/fedora-29-x...
At the end of the file, we can see: !! Copr timeout => sending INT Traceback (most recent call last): File "/usr/bin/copr-rpmbuild", line 158, in main action(args, config) File "/usr/bin/copr-rpmbuild", line 295, in build_rpm builder.run() File "/usr/lib/python3.6/site-packages/copr_rpmbuild/builders/mock.py", line 40, in run self.produce_rpm(srpm, configdir, self.resultdir) File "/usr/lib/python3.6/site-packages/copr_rpmbuild/builders/mock.py", line 124, in produce_rpm raise RuntimeError("Build failed") RuntimeError: Build failed
The following links are examples of Chromium 72.0.3626.119 builds. For Fedora 29, it takes 3 times to succeed. I consider it the normal case. https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/861455/ https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/861866/ https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/862016/
This is likely the worst case. The build for Fedora 28 takes 7 times to succeed. Sometimes I just click 'Resubmit' without reading the log file. https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/861455/ https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/861866/ https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/862229/ https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/862543/ https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/862972/ https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/863432/ https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/863699/
While the normal case takes about 3 days to get a successful build, the worst case takes about 9 days.
On Sunday, March 10, 2019 6:29:15 PM CET 藍挺瑋 wrote:
What does 'Copr timeout => sending INT' mean in builder-live.log?
It means that the timeout (for any build in copr) isreached, and Copr is sending the SIGINT signal to the scripting; and if the signal was blocked, copr would even even try to send SIGKILL after certain period of time ... This is to give the build script a chance to cleanup and end nicely.
This problem has existed for a long time and it often shows in my Chromium builds. While it is possible to click 'Resubmit' on failed builds and it usually takes 1 or 2 rebuilds to get successful builds, having to do the same thing for each Chromium update takes a lot of time because each build usually takes more than 15 hours.
I guess chromium would need a slightly longer timeout then.
Pavel
Pavel Raiskup 於 2019/3/11 下午3:49 寫道:
On Sunday, March 10, 2019 6:29:15 PM CET 藍挺瑋 wrote:
What does 'Copr timeout => sending INT' mean in builder-live.log?
It means that the timeout (for any build in copr) isreached, and Copr is sending the SIGINT signal to the scripting; and if the signal was blocked, copr would even even try to send SIGKILL after certain period of time ... This is to give the build script a chance to cleanup and end nicely.
Thanks for you reply. It looks like the timeout is set to 18 hours.
This problem has existed for a long time and it often shows in my Chromium builds. While it is possible to click 'Resubmit' on failed builds and it usually takes 1 or 2 rebuilds to get successful builds, having to do the same thing for each Chromium update takes a lot of time because each build usually takes more than 15 hours.
I guess chromium would need a slightly longer timeout then.
I guess it may be possible to build Chromium faster by disabling debug symbols, but debug packages are very useful when I have to understand the reason of Chromium crashes.
Pavel
copr-devel@lists.fedorahosted.org