Skip to content

cmd/go: TestScript failures #66337

@gopherbot

Description

@gopherbot
#!watchflakes
default <- pkg == "cmd/go" && test == "TestScript" &&
           output !~ `The process cannot access the file because it is being used by another process.`  # tracked in go.dev/issue/71112

Issue created automatically to collect these failures.

Example (log):

vcs-test.golang.org rerouted to http://127.0.0.1:55618
https://vcs-test.golang.org rerouted to https://127.0.0.1:55619
go test proxy running at GOPROXY=http://127.0.0.1:55620/mod
--- FAIL: TestScript (1.26s)
    --- FAIL: TestScript/gotoolchain_loop (5.24s)
        script_test.go:136: 2024-03-15T11:17:42Z
        script_test.go:138: $WORK=/tmp/buildlet/tmp/cmd-go-test-1876406220/tmpdir1229658131/gotoolchain_loop606090653
        script_test.go:160: 
            > env GOTOOLCHAIN=auto
            > env TESTGO_VERSION=go1.21.1
            # Basic switch should work. (1.183s)
            # Toolchain target mismatch should be detected. (0.238s)
            # Toolchain loop should be detected. (3.799s)
            > env TESTGO_VERSION_SWITCH=loop
            > ! go version
            [signal: illegal instruction]
            > stderr -count=10 '^go: switching from go1.21.1 to go1.21.99 \[depth 9[0-9]\]$'
        script_test.go:160: FAIL: testdata/script/gotoolchain_loop.txt:17: stderr -count=10 '^go: switching from go1.21.1 to go1.21.99 \[depth 9[0-9]\]$': found 0 matches for `(?m)^go: switching from go1.21.1 to go1.21.99 \[depth 9[0-9]\]$` in stderr

watchflakes

Metadata

Metadata

Assignees

No one assigned

    Labels

    NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions