Michael Soegtrop (Sep 23 2022 at 09:48): Michael Soegtrop (Sep 23 2022 at 09:48):@Théo Zimmermann : I recently have on Windows a timeout failure rate of guessed 1/3. Usually it gets through in 5h20 or so, but it happens regularly that it exceeds 7h. Can we extend the timeout to 8h? I think after the release I will create an option for "long compile time packages" and check these less frequently - or in a separate CI run. They tend to be not problematic.
If I remember right, you extended it to 6h last time I had issues.
Théo Zimmermann (Sep 23 2022 at 11:07):No, you are confusing with GitLab. On GitHub Actions there is a hard limit at 6 hours per job.
Théo Zimmermann (Sep 23 2022 at 11:08):The only solution to workaround such a timeout issue is to split the job into multiple jobs.
Théo Zimmermann (Sep 23 2022 at 11:08):Is this something that would be realistic to do? The jobs can share artifacts.
Théo Zimmermann (Sep 23 2022 at 11:09):Note that such splitting could also be used to reduce the workflow time by parallelizing some builds (if realistic).
Michael Soegtrop (Sep 23 2022 at 12:14):@Théo Zimmermann : it makes sense to disable 3 or 4 long runners in CI - things like unimath. They anyway don't have a tendency to create install issues (this is what Coq Platform CI detects). But of course one has to enable them for release build. Modular builds I would delay until we have modular installers.
Last updated: Jun 03 2023 at 05:01 UTC