cmd/go: test failure on mod_sumdb_file_path on module retraction CLs #41078
Labels
FrozenDueToAge
modules
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
After I submitted the module retraction CLs yesterday (ending with CL 228384), I noticed a few test failures on the long test builders in the middle of the series:
c769f034d796769ad10fc03fe6866b36039d1a09
: https://build.golang.org/log/cac23bbc7791016925d1ed54b46972b54376ebedc769f034d796769ad10fc03fe6866b36039d1a09
: https://build.golang.org/log/e817e5df39a7cf17e3f5825197b32eb482d453f30bbd386e8bbdf419077d708d3671245fc0f50f0c
: https://build.golang.org/log/16963f6a46598db563938acc8bb08ee0abb59acdeb3e27ac1a9346c7c2669ba2b863811607eddeae
: https://build.golang.org/log/48b72534759657e46ba0742ba9cb98dc71d2b1a50bbd386e8bbdf419077d708d3671245fc0f50f0c
: https://build.golang.org/log/fd731ff3f990dbb7bd870b1b230a6f9241df20e7The failure looks like this:
Essentially, the test is running
go get -d golang.org/x/text@v0.3.2
with an empty module cache. It then deletesgo.sum
and uses the old module cache as a proxy with sumdb support and runs the same command again.The error indicates the local sumdb lookup was successful, but the tile was missing. I'm not sure why that would happen. Both commands should retrieve the same set of tiles. The first command should fail if it wasn't able to retrieve a tile. The second command should succeed if the tile is present.
The error stopped happening after CL 228383. That might cause new tiles to be fetched for
v0.3.3
, but it shouldn't affect whether a tile is fetched forv0.3.2
. The error didn't happen consistently across builders, and I haven't been able to reproduce it, either locally or with a linux-amd64 gomote.The text was updated successfully, but these errors were encountered: