stdout 'diff current/go.sum tidy/go.sum'

# Everything is tidy, should return zero exit code.
go mod tidy
go mod tidy -diff
! stdout 'diff current/go.mod tidy/go.mod'
! stdout 'diff current/go.sum tidy/go.sum'

# go.mod requires updates, should return non-zero exit code.
cp go.mod.orig go.mod
! go mod tidy -diff
stdout 'diff current/go.mod tidy/go.mod'
! stdout 'diff current/go.sum tidy/go.sum'
cmp go.mod.orig go.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'

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 .

# Regression test for #56222: 'go get -t' and 'go mod tidy'
# should save enough checksums to run 'go test' on the named
# packages or any package in "all" respectively.

# 'go mod tidy' in a module at go 1.21 or higher should preserve
# checksums needed to run 'go test all'.
cd m1
go mod tidy

go list -f '{{if eq .ImportPath "example.com/generics"}}{{.Module.GoVersion}}{{end}}' -deps -test example.com/m2/q
stdout 1.18
[!short] go test -o $devnull -c all

# If we replace the module and run 'go mod tidy', we should get a sum for the replacement.
go mod edit -replace rsc.io/quote@v1.5.0=rsc.io/quote@v1.5.1
go mod tidy
grep 'rsc.io/quote v1.5.1' go.sum
cp go.sum go.sum.tidy

# 'go mod vendor' should preserve that sum, and should not need to add any new entries.
go mod vendor
grep 'rsc.io/quote v1.5.1' go.sum
cmp go.sum go.sum.tidy

-- go.mod --
module golang.org/issue/27868

# 'go mod tidy' should not panic if the main module initially
# requires an older version of itself.

# A module may require an older version of itself without error. This is
# inconsistent (the required version is never selected), but we still get
# a reproducible build list.
go list -m all
stdout '^golang.org/issue/46078$'

# 'go mod tidy' should fix this (and not crash).
go mod tidy

#
# If a 'replace' directive specifies an older-than-selected version of a module,
# 'go mod tidy' shouldn't try to add that version to the build list to resolve a
# missing package: it won't be selected, and would cause the module loader to
# loop indefinitely trying to resolve the package.

cp go.mod go.mod.orig

! go mod tidy
! stderr panic

# but the new import is from what is initially a test-only dependency.

# Control case: in Go 1.14, the original go.mod is tidy,
# and the dependency on c is eagerly loaded.

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

go list -m all
stdout '^a v0.1.0 '
stdout '^b v0.1.0 '
stdout '^c v0.1.0 '

# After adding a new import of b/y,

env GO111MODULE=on

# Regression test for golang.org/issue/27063:
# 'go mod tidy' and 'go mod vendor' should not hide loading errors.

! go mod tidy
! stderr 'package nonexist is not in std'
stderr '^go: issue27063 imports\n\tnonexist.example.com: cannot find module providing package nonexist.example.com'
stderr '^go: issue27063 imports\n\tissue27063/other imports\n\tother.example.com/nonexist: cannot find module providing package other.example.com/nonexist'

# Regression test for https://go.dev/issue/60313: 'go mod tidy' did not preserve
# dependencies needed to prevent 'ambiguous import' errors in external test
# dependencies.

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

-- go.mod --
module example

go 1.21

require (
	example.net/a v0.1.0
	example.net/b v0.1.0
)

require example.net/outer/inner v0.1.0 // indirect

replace (
	example.net/a v0.1.0 => ./a