Closed bcmills closed 2 years ago
Curiously, a similar failure mode has also occurred with 502 Bad Gateway
:
greplogs --dashboard -md -l -e 'getting corpus: .*: 502 Bad Gateway'
We can mark the test as known flaky sooner.
greplogs -l -e 'syncing segment \d+: .*: 416 Requested Range Not Satisfiable' --since=2022-02-16
2022-05-06T16:18:34-b8613e0-5fcd1ba/windows-amd64-longtest
2022-03-17T18:03:05-e0ed2a2-0fca8a8/linux-amd64-longtest
The 502 Bad Gateway from /logs is another (non-serious) issue, filed #53569 for it.
I was going to send a small change to add a log line, to learn what range value causes the server to respond with 416, but we already have this log line and can see from the log that this is caused by issue #26922. Sent CL 414434 for it.
Change https://go.dev/cl/414434 mentions this issue: maintner: don't try to download negative bytes
The aforementioned failure is from golang/build@950e098e856eb0b5ad1cea40a7582a0632bb2616, which is a few commits before CL 414434 (golang/build@4443b1072da90af1a0a577f3211e6bee3a45c22c).
Tentatively closing since I expect this should be completely fixed and there's nothing more to do here, but please reopen if there are further occurrences after the aforementioned commit.
This failure mode seems to occur fairly frequently on
windows/amd64
, and somewhat less frequently onlinux/amd64
:greplogs --dashboard -md -l -e 'syncing segment \d+: .*: 416 Requested Range Not Satisfiable'
(CC @golang/release)