Separate timeout for "preparation" and actual building
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 322
- Forks
- 171
- PR merge metrics
- No merged PRs in 30d
Description
The test for Cassandra, that I'm extending in NixOS/nixpkgs#59179 doesn't work on ofBorg because it times out: https://logs.nix.ci/?key=nixos/nixpkgs.59179&attempt_id=785a4098-3371-4f2b-81c6-61a4d1125ee3
The test was run only for three minutes (takes 6 on my laptop) but it was terminated because the entire evaluation took more than thirty minutes.
I haven't looked into how exactly ofBorg handles timeouts but I think we could have a different timeout for evaluating the expressions and fetching dependencies and another one for actually building the package/test.
What's actually happening in those 30 mins? When does the timout start counting? I s it really the fetching of the deps that takes so long?
Contributor guide
No contributing guide indexed for this repository
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 the linked ofBorg log and the Cassandra test changes in NixOS/nixpkgs#59179; determine when the current 30-minute evaluation timeout begins and whether dependency fetching accounts for it. Done means documenting the timing and defining separate limits for evaluation or dependency fetching and package or test building.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100