Since ld.gold segfault on Fedora 33 and rawhide when it uses more than one thread [1], I switched my Chromium builds to use ld.bfd a few months ago. The change increased the build time, but at least the build didn't fail in 1 hour due to ld.gold segfault. It seems that Chromium 87 increases the build time further with its Ozone platform. Now it is very hard to get successful builds of Chromium 87 on Copr. After submitting Chromium 87.0.4280.66 builds for more than 10 times, I still couldn't get successful builds for all chroots. Even if there were successful builds in some chroots, the build time was pretty close to the limit. For example, this build [2] took 29h 50m for Fedora 33, and this build [3] took 29h 52m for Fedora rawhide. Is it possible to raise the limit again? Given that Chromium keeps increasing the build time for the past 2 years, I think we should raise the limit to 48 hours this time. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1873848 [2] https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/1782394/ [3] https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/1794997/ _______________________________________________ copr-devel mailing list -- copr-devel(a)lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave(a)lists.fedorahosted.org 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/copr-devel@lists.fedorahoste...

Jakub Kadlcik 於 2020/12/6 下午8:57 寫道: > Hello, > I increased the max build time limit to 48h as you requested. Thank you. I got a successful build of Chromium 87.0.4280.88 several days ago [1]. It took about 31 hours. > Just for reference if someone else is reading this, it is not a > default build time, that remains 5h. But it is possible to specify a > higher value, please see > https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html#per-build... > > > Jakub [1] https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/1816762/

Thank you for keeping us posted. It is interesting to know how long the biggest packages take. Jakub On Sun, Dec 13, 2020 at 5:20 PM 藍挺瑋 <lantw44(a)gmail.com&gt; wrote: > Jakub Kadlcik 於 2020/12/6 下午8:57 寫道: >> Hello, >> I increased the max build time limit to 48h as you requested. > Thank you. I got a successful build of Chromium 87.0.4280.88 several > days ago [1]. It took about 31 hours. > >> Just for reference if someone else is reading this, it is not a >> default build time, that remains 5h. But it is possible to specify a >> higher value, please see >> https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html#per-build... >> >> >> Jakub > [1] https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/1816762/ > _______________________________________________ copr-devel mailing list -- copr-devel(a)lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave(a)lists.fedorahosted.org 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/copr-devel@lists.fedorahoste...

On 2/8/21 11:16 AM, Jean-Marc Liger wrote: > Hi, > > I'm looking for to increase the build time in copr's web interface, > but I didn't find any entry for that, do I missed something ? > > Jean-Marc Hi, when you create a new build by clicking on New Build in your project, you will also see 3. Select chroots and other options and there you can select the desired timeout (box Timeout). Silvie

hum IMHO should be available on general settings . for example when we want build kernels

On Mon, 2021-03-08 at 08:52 +0100, Miroslav Suchý wrote: > Dne 02. 03. 21 v 17:26 Sérgio Basto napsal(a): > > hum IMHO should be available on general settings . for example > > when > > we want build kernels > > This is question of balance. Nearly all knobs can be sometimes > useful > in Project settings, chroot settings, package > settings, build settings. > Having them on all places would be UI nightmare. I am open to > discussion, but we have to consider other projects and > other users as well. Moving settings here and there is dead way. I understand, I always try to look for the most user friendly approach, and the general settings seem to me the most user friendly place. This is my suggestion. The global setting could be the default value of "when you create a new build by clicking on New Build in your project, you will also see 3. Select chroots and other options and there you can select the desired timeout (box Timeout)".

--