ocaml-benchmarks: unexpected disconnect
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 42
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
This kind of error seems more common these days:
#13 [ 9/13] RUN git -C opam-repository fetch origin 26770281fa1ea8b13aab979c1dfbd326e9ab512c
#13 73.79 error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8)
#13 73.79 error: 3198 bytes of body are still expected
#13 73.80 fetch-pack: unexpected disconnect while reading sideband packet
#13 73.80 fatal: early EOF
#13 73.80 fatal: index-pack failed
#13 ERROR: process "/bin/sh -c git -C opam-repository fetch origin $OPAMREPOSHA" did not complete successfully: exit code: 128
i've seen it 3 or 4 times in the past couple of weeks.
Full log: https://bench.ci.dev/_pipeline/job/2024-07-11/173146-ocluster-build-950d57
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 full log and the failing git -C opam-repository fetch origin $OPAMREPOSHA build step. Investigate why the fetch intermittently ends with an HTTP/2 cancellation, early EOF, and index-pack failure. Done means the ocaml-benchmarks build no longer fails from this unexpected disconnect, with the behavior verified in the relevant pipeline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, git
- Domain
- build-system, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100