blob: 6ff1eb51cb088b50e6f947de7d862a6d98406b34 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
|
env GO111MODULE=on
# We should not create a go.mod file unless the user ran 'go mod init' explicitly.
# However, we should suggest 'go mod init' if we can find an alternate config file.
cd $WORK/test/x
! go list .
stderr 'found .git/config in .*[/\\]test'
stderr '\s*cd \.\. && go mod init'
# The command we suggested should succeed.
cd ..
go mod init
go list -m all
stdout '^m$'
# We should not suggest creating a go.mod file in $GOROOT, even though there may be a .git/config there.
cd $GOROOT
! go list .
! stderr 'go mod init'
# We should also not suggest creating a go.mod file in $GOROOT if its own
# .git/config has been stripped away and we find one in a parent directory.
# (https://golang.org/issue/34191)
env GOROOT=$WORK/parent/goroot
cd $GOROOT
! go list .
! stderr 'go mod init'
cd $GOROOT/doc
! go list .
! stderr 'go mod init'
-- $WORK/test/.git/config --
-- $WORK/test/x/x.go --
package x // import "m/x"
-- $WORK/parent/.git/config --
-- $WORK/parent/goroot/README --
This directory isn't really a GOROOT, but let's pretend that it is.
-- $WORK/parent/goroot/doc/README --
This is a subdirectory of our fake GOROOT.
|
