On Tuesday, June 9, 2020 7:43:06 PM CEST Pavel Raiskup wrote: > On Tuesday, June 9, 2020 4:44:35 PM CEST 藍挺瑋 wrote: > > It looks like both GCC 10 and Chromium 83 increase the time required to > > build Chromium. I know the build time limit was just raised to 24 hours > > a few months ago, but recent releases of Chromium 83 started to exceed > > the limit on Fedora 32 and rawhide: > > > > https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/1404528/ > > https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/1406157/ > > https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/1424921/ > > https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/1427639/ > > > > Do you think we can raise the limit to 30 hours this time? Currently > > all successful builds of Chromium 83 with GCC 10 take 23 hours, which > > is close to the time limit. > > We are are even now over the sane default build time limit, and raising it > even more doesn't make much sense to me. I'd rather propose to > concentrate on implementing default build timeout (set to say 2hours), and > allow people to pick timeout according to the package needs (say from 15 > minutes up to 30hours). > > I reused this bug https://pagure.io/copr/copr/issue/1303 as the original > problem was slightly related.
Let me change my mind, as I see that we have no problems with computational power and long-term running jobs ATM. I'm going to raise the timeout to 30 hours till we have better solution (issue 1303). If the timeout becomes a sudden problem, we can decrease it promptly again. Pavel _______________________________________________ copr-devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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.fedorahosted.org/archives/list/[email protected]
