New timeout not taken into account?
Nobody has claimed this yet.
- Dominant language
- PLpgSQL
- Stars
- 1.6k
- Forks
- 358
- Avg merge
- 20h 30m
- Merged PRs (30d)
- 27
Description
staging-20.09 is blocked on what seems to be an infrastructure issue.
https://hydra.nixos.org/build/129420286#tabs-buildsteps keeps timing out. Nothing significant has changed for ghc compilation since current release-20.09 which takes 78% of the timeout limit.
I've attempted to increase the timeout, but it doesn't seem to take effect.
I suspect this is a bug where the timeout is only set when a drv is registered for the first time.
Other than that, the increase in build time could be indicative of an issue on the build machines.
I've also noticed that most mac*-guest build machines are unreachable.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Hydra build 129420286 and compare its timeout behavior with build 127601467, then review the attempted timeout increase in nixpkgs pull request 103007. Determine why the new timeout is not applied and verify that a corrected setting affects GHC builds; separately assess whether unreachable mac*-guest machines are contributing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- build-system, ci-cd, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100