Unsupported system type status error message misleading
Nobody has claimed this yet.
- Dominant language
- PLpgSQL
- Stars
- 1.6k
- Forks
- 358
- Avg merge
- 20h 30m
- Merged PRs (30d)
- 27
Description
~10000 jobs for the experimental armv7l jobset (which is basically all of them) started failing with the status error message "Unsupported system type" 3 days ago.
I asked @grahamc on IRC about it and he told be it happened because no armv7 builders became available in time.
That is a thing that can happen of course but the error message sounds nothing like the actual error to me. "Timed out while waiting for available builders" (or something along those lines) would be much clearer.
The jobs' failures are also propagated onto subsequent builds which doesn't make a lot of sense since the error is most likely to be a temporary outage of the infrastructure, not a problem of the actual build.
I'm not too familiar with Hydra yet to but this might be a duplicate of #40.
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
The report concerns Hydra's builder-availability timeout and the propagation of resulting failures; no source file or test is named. Start by locating the code that emits "Unsupported system type" and compare the behavior with duplicate candidate #40; done means a no-builder timeout is reported accurately and does not incorrectly propagate to subsequent builds.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100