Aaron Durbin via coreboot wrote:
We are observing since 3 days instabilities while cherry-picking patches from coreboot.org:
git fetch https://review.coreboot.org/coreboot refs/changes/40/52140/3 && git cherry-pick FETCH_HEAD
fatal: The remote end hung up unexpectedly
fatal: protocol error: bad pack header
This is happening on several machines, our automation is also impacted. Any change/issue that could explain such behavior?
I think it's on your end, Selma. Perhaps the git repo got corrupted?
..
The root cause is likely the first error: remote end hung up unexpectedly. The following might be helpful.
https://stackoverflow.com/questions/6842687/the-remote-end-hung-up-unexpecte...
My guess is either a change in an outgoing proxy at Intel or that all your repos changed in the same way at the same time to now interact badly with how outgoing proxying has always worked. (HTTP request larger than http.postBuffer git config setting leading to HTTP/1.1 chunked transfer.)
Also if there's a way to get more verbose logging out that might help point in the right direction.
Do try (from that stackoverflow):
# Linux export GIT_TRACE_PACKET=1 export GIT_TRACE=1 export GIT_CURL_VERBOSE=1
#Windows set GIT_TRACE_PACKET=1 set GIT_TRACE=1 set GIT_CURL_VERBOSE=1
Before the git command, and see what comes out.
//Peter