於 星期六，2019-12-21 於 09:53 +0100，Pavel Raiskup 提到：
On Saturday, December 21, 2019 4:40:31 AM CET 藍挺瑋 wrote:
> Chromium project has decided to remove a feature called 'jumbo build'
> from its build system:
> While this feature still exists in the build system of Chromium 79, it
> no longer builds and bugs related to jumbo build are considered WONTFIX:
> Therefore, I must disable jumbo build to get a working build of Chromium
> 79. Disabling the features significantly increases the number of build
> targets from about 25000 to 41000, causing the build time to reach the
> limit of Copr, which is currently 21 hours.
> Is it possible to raise the limit again to avoid the timeout? Otherwise,
> it is likely that building Chromium will become harder over time because
> Chromium build time keeps increasing.
Hi, what timeout do you need for chromium jumbo build? I see we have
misconfigred frontend/backend pair (21h vs 24h), so we should fix that...
but I'm not sure 24h would actually help.
For jumbo build (the fast one, used in my Chromium 73 ~ 78 builds), each
successful build takes about 8 ~ 10 hours.
For non-jumbo build (the slow one, used in my Chromium 79 builds), each
successful build takes about 18 ~ 19 hours.
I don't know how can I measure the build time on Copr because I have no chance
to run a build job for more than 21 hours. The 3 failed jobs I listed above hit
timeout at different steps:
1129111: extracting debug info
1129703: linking the final executable (progress: 41636/41637)
1131005: compiling source files (progress: 38922/41581)
I guess 24 hours is enough for the slowest one. Chromium upstream keeps
increasing the build time, so I can't know if I will have to request change to
build time limit again.