blob: cee055eabe9c26d0c1d6c4ca79d3b2121eb29956 [file] [log] [blame]
# This test verifies that line numbers are included in module import errors.
# Verifies golang.org/issue/34393.
go list -e -mod=mod -deps -f '{{with .Error}}{{.Pos}}: {{.Err}}{{end}}' ./main
stdout '^bad[/\\]bad.go:3:8: malformed import path "šŸ§.example.com/string": invalid char ''šŸ§''$'
# TODO(#26909): This should include an import stack.
# (Today it includes only a file and line.)
! go build ./main
stderr '^bad[/\\]bad.go:3:8: malformed import path "šŸ§.example.com/string": invalid char ''šŸ§''$'
# TODO(#41688): This should include a file and line, and report the reason for the error..
# (Today it includes only an import stack.)
! go get -d ./main
stderr '^m/main imports\n\tm/bad imports\n\tšŸ§.example.com/string: malformed import path "šŸ§.example.com/string": invalid char ''šŸ§''$'
-- go.mod --
module m
go 1.13
-- main/main.go --
package main
import _ "m/bad"
func main() {}
-- bad/bad.go --
package bad
import _ "šŸ§.example.com/string"