| Server IP : 88.222.222.85 / Your IP : 216.73.216.171 Web Server : LiteSpeed System : Linux lt-bnk-web922.main-hosting.eu 4.18.0-553.141.2.lve.el8.x86_64 #1 SMP Wed Jul 8 16:10:02 UTC 2026 x86_64 User : u970350538 ( 970350538) PHP Version : 7.4.33 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : OFF | Python : OFF | Sudo : OFF | Pkexec : OFF Directory : /opt/golang/1.22.0/src/cmd/go/testdata/script/ |
Upload File : |
env TESTGO_VERSION=go1.21.0 env TESTGO_VERSION_SWITCH=switch # If the main module's go.mod file lists a version lower than the version # required by its dependencies, the commands that fetch and diagnose the module # graph (such as 'go mod graph' and 'go mod verify') should fail explicitly: # they can't interpret the graph themselves, and they aren't allowed to update # the go.mod file to record a specific, stable toolchain version that can. ! go mod verify stderr '^go: rsc.io/future@v1.0.0: module rsc.io/future@v1.0.0 requires go >= 1.999 \(running go 1.21.0\)' ! go mod graph stderr '^go: rsc.io/future@v1.0.0: module rsc.io/future@v1.0.0 requires go >= 1.999 \(running go 1.21.0\)' # TODO(#64008): 'go mod download' without arguments should fail too. # 'go get' should update the main module's go.mod file to a version compatible with the # go version required for rsc.io/future, not fail. go get . stderr '^go: module rsc.io/future@v1.0.0 requires go >= 1.999; switching to go1.999testmod$' stderr '^go: upgraded go 1.21 => 1.999$' stderr '^go: added toolchain go1.999testmod$' # Now, the various 'go mod' subcommands should succeed. go mod download go mod verify go mod graph -- go.mod -- module example go 1.21 require rsc.io/future v1.0.0 -- example.go -- package example import _ "rsc.io/future"