golang/go

cmd/go: TestScript/mod_import failure on darwin-amd64-nocgo

Open

#35,285 opened on Oct 31, 2019

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (19,008 forks)batch import
GoCommandNeedsInvestigationOS-Darwinhelp wanted

Repository metrics

Stars
 (133,883 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

darwin-amd64-nocgo (https://build.golang.org/log/b64b26f0f1ea99d0a15dbe847285ee310af7fae9):

go test proxy running at GOPROXY=http://127.0.0.1:57008/mod
go proxy: no archive rsc.io v1.1.0: file does not exist
go proxy: no archive rsc.io v1.5.2: file does not exist
go proxy: no archive rsc.io v1.0.0: file does not exist
go proxy: no archive rsc.io v1.0.0: file does not exist
go proxy: no archive rsc.io v1.0.0: file does not exist
go proxy: no archive rsc.io v1.0.0: file does not exist
go proxy: no archive rsc.io v1.5.1: file does not exist
go proxy: no archive example.com/newcycle v1.0.0: file does not exist
go proxy: no archive rsc.io v1.5.2: file does not exist
--- FAIL: TestScript (0.01s)
    --- FAIL: TestScript/mod_import (0.79s)
        script_test.go:192: 
            # latest rsc.io/quote should be v1.5.2 not v1.5.3-pre1 (0.648s)
            > go list
            [stdout]
            x
            > go list -m all
            [stdout]
            x
            > stdout 'rsc.io/quote v1.5.2'
            FAIL: testdata/script/mod_import.txt:6: no match for `(?m)rsc.io/quote v1.5.2` found in stdout
            
FAIL
FAIL	cmd/go	251.813s

I'm not sure what to make of this, but the file does not exist error suggest perhaps filesystem flakiness. (There is precedent for the filesystem being flaky in #33041.)

CC @jayconrod

Contributor guide

Research direction
Investigate why the test fails on darwin amd64 nocgo. The error 'no archive' suggests the test proxy cannot serve the required module versions. Check if the test data files are missing or if there is a filesystem issue. Also verify the expected version v1.5.2 is present.
Tech stack
go
Domain
devtools
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoTesting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70