ghc*: Increase build timeout to 1 day #103008
Merged
+11
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation for this change
The default of 10 hours is insufficient for some of the slower platforms like macOS and aarch64.
The timeout failures have been causing delays and waste of build agent time on staging-20.09, quite opposite of the intent of the timeout feature.
I've decided not to tune the timeout per system type, because I don't expect GHC to have this kind of problem, and if it does, it would normally be caught by the lack of build log output after two hours. The
timeout
is a last resort for builds/tests that loop while printing to the log. So decreasing the timeout forx86_64-linux
would be over-engineered.Things done
Applied this to staging-20.09 #103007 which should soon merge into release-20.09.
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)