oxidecomputer / oxidecomputer/omicron
test failed in CI: [nextest installation]
Open
Nobody has claimed this yet.
Test Flake
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
This test failed on a CI run on "main":
https://github.com/oxidecomputer/omicron/runs/64258375971
Log showing the specific test failure:
Excerpt from the log showing the failure:
+ curl -sSfL --retry 10 https://get.nexte.st/0.9.125/linux
+ gunzip
+ tar -xvf - -C /home/build/.cargo/bin
curl: (56) OpenSSL SSL_read: Connection reset by peer, errno 104
cargo-nextest
gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
The --retry helps here for issues seen while starting the download, but not for mid-download problems due to it being piped:
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 .github/buildomat/build-and-test.sh at line 25 and review how the cargo-nextest download is piped through curl, gunzip, and tar. Use the linked CI run and log to confirm the failure mode, then verify that a mid-download interruption is handled and the CI installation completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, shell
- Domain
- build-system, ci-cd, devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100