1
0
mirror of https://github.com/golang/go synced 2024-11-13 16:10:25 -07:00

cmd/go: deflake TestScript/gcflags_patterns

The check below can fail incorrectly if the buildid ends with '-p'.

    ! stderr 'compile.* -e .*-p [^z]'

This fix changes regular expressions to '-e.* -p' or '-N.* -p' instead
of '-e .*-p'. '-l' is no longer used because the compiler accepts
multiple flags starting with '-l' ('-e' and '-N' do not have this
problem), so there could be false matches.

Change-Id: I827c411de28624019a287f853acc9666e87cbfb9
Reviewed-on: https://go-review.googlesource.com/c/156327
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
This commit is contained in:
Jay Conrod 2019-01-04 17:30:36 -05:00
parent 73fb3c38a6
commit e1b903788a

View File

@ -21,9 +21,9 @@ stderr 'compile.* -p y'
go build -n -v -gcflags=' z1 = -e ' z1
stderr 'compile.* -e.* -p z1'
# -gcflags='all=-N -l' should apply to all packages, even with go test
go test -c -n -gcflags='all=-N -l' z1
stderr 'compile.* -N -l .*-p z3 '
# -gcflags='all=-e' should apply to all packages, even with go test
go test -c -n -gcflags='all=-e' z1
stderr 'compile.* -e.* -p z3 '
# -ldflags for implicit test package applies to test binary
go test -c -n -gcflags=-N -ldflags=-X=x.y=z z1