@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.
No, you are confusing with GitLab. On GitHub Actions there is a hard limit at 6 hours per job.
The only solution to workaround such a timeout issue is to split the job into multiple jobs.
Is this something that would be realistic to do? The jobs can share artifacts.
Note that such splitting could also be used to reduce the workflow time by parallelizing some builds (if realistic).
@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: Feb 22 2024 at 05:02 UTC