# this end state is stable.

go mod tidy -e
cmp go.mod go.mod.tidye


# An explicit 'go get' with the correct versions should allow 'go mod tidy' to
# succeed and remain stable. y.1 does not upgrade x, and can therefore be used
# with it.

go get example.net/x@v0.1.0 example.net/y@v0.1.0
go mod tidy
cmp go.mod go.mod.postget


# The 'tidy' logic for a lazy main module is somewhat different from that for an

# This test checks that "go mod tidy -x" print
# commands tidy executes.
# Verifies golang.org/issue/35849

rm $GOPATH/pkg/mod/cache/download/rsc.io/quote
go mod tidy
! stderr 'get '$GOPROXY

rm $GOPATH/pkg/mod/cache/download/rsc.io/quote
go mod tidy -x
stderr 'get '$GOPROXY

-- go.mod --
module example.com/mod

-- a.go --
package mod

! stderr '\n\tgo mod tidy'

cmp go.mod go.mod.tidy

# Make sure that -diff behaves the same as tidy.
[exec:patch] cp go.mod go.mod.tidyResult
[exec:patch] ! exists go.sum
[exec:patch] cp go.mod.orig go.mod
[exec:patch] ! go mod tidy -e -diff
[exec:patch] stdout 'diff current/go.mod tidy/go.mod'

go mod tidy -e
cmp go.mod go.mod.tidye2

go mod tidy -e
cmp go.mod go.mod.tidye3

go mod tidy -e
cmp go.mod go.mod.orig


# If we upgrade away all of the packages simultaneously, the resulting tidy
# state converges at "no dependencies", because simultaneously adding all of the

# go.sum should list directly used modules and dependencies
go get rsc.io/quote@v1.5.2
go mod tidy
grep rsc.io/sampler go.sum

# go.sum should not normally lose old entries
go get rsc.io/quote@v1.0.0
grep 'rsc.io/quote v1.0.0' go.sum
grep 'rsc.io/quote v1.5.2' go.sum
grep rsc.io/sampler go.sum

# go mod tidy should clear dead entries from go.sum
go mod tidy
grep 'rsc.io/quote v1.0.0' go.sum
! grep 'rsc.io/quote v1.5.2' go.sum

cp go.mod go.mod.orig
go mod tidy
cmp go.mod go.mod.orig

# Make sure that -diff behaves the same as tidy.
[exec:patch] mv go.mod go.mod.tidyResult
[exec:patch] mv go.sum go.sum.tidyResult
[exec:patch] cp go.mod.orig go.mod
[exec:patch] ! go mod tidy -diff
[exec:patch] cp stdout diff.patch
[exec:patch] exec patch -p1 -i diff.patch
[exec:patch] go mod tidy -diff
[exec:patch] ! stdout .

cp go.mod go.mod.orig
go mod tidy
cmp go.mod go.mod.orig

# Make sure that -diff behaves the same as tidy.
[exec:patch] mv go.mod go.mod.tidyResult
[exec:patch] mv go.sum go.sum.tidyResult
[exec:patch] cp go.mod.orig go.mod
[exec:patch] ! go mod tidy -diff
[exec:patch] cp stdout diff.patch
[exec:patch] exec patch -p1 -i diff.patch
[exec:patch] go mod tidy -diff
[exec:patch] cmp go.mod go.mod.tidyResult

      - ACCEPT_EULA=Y
      - SA_PASSWORD=LoremIpsum86
      - MSSQL_DB=gorm
      - MSSQL_USER=gorm
      - MSSQL_PASSWORD=LoremIpsum86
  tidb:
    image: 'pingcap/tidb:v6.5.0'
    ports:
      - "9940:4000"

cmp go.mod go.mod.orig

# Make sure that -diff behaves the same as tidy.
[exec:patch] cp go.mod.orig go.mod
[exec:patch] ! exists go.sum
[exec:patch] ! go mod tidy -diff
[exec:patch] ! stdout .

go list -mod=mod all
! stdout '^example.com/testdep$'
cmp stdout list-1.txt
cmpenv go.mod go.mod.untidy

go mod tidy
cmpenv go.mod go.mod.tidy

# On the other hand, if we jump straight to 'go mod tidy',
# the requirements remain tidy from the start.

cp go.mod.orig go.mod
go mod tidy
cmpenv go.mod go.mod.tidy


# The updated version should have been written back to go.mod, so now the 'go'