Evaluate using hydra-eval-jobs
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 323
- Forks
- 171
- PR merge metrics
- No merged PRs in 30d
Description
Context:
Ofborg should eval using hydra-eval-jobs, for an in-depth evaluation.
Though, with that particular failure (b3ef282fd5c37d98b550e04c596136db8a9e978b), hydra-eval-jobs did not return the error. The only output was:
hydra-eval-jobs returned exit code 1:
error: unexpected EOF reading a line
An strace of this revealed that something transmitted the error, but also something read all of the error.
For appropriate CI use, the error would have to be available, otherwise, it's a wild goose chase. (This is actually an Hydra issue though.)
Another concern, is that this evaluation takes quite a long time. At least it does on my 2012-era Xeon workstation. I wonder if that would cause additional undue load on ofborg.
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
No implementation file or test is named. Start by reproducing the evaluation for commit b3ef282fd5c37d98b550e04c596136db8a9e978b with hydra-eval-jobs, then inspect how Ofborg receives its error output and measure the evaluation time. Done means errors remain available for CI investigation without imposing undue load on Ofborg.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100