You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a workaround for a change in behaviour between go <= 1.9 and go
1.10.
Prior to go 1.9, compiling a test would not fail if the specified
output dir does not exist. However, it does fail in go 1.10.
By failing when the the directory does not exist, we have a consistent
behaviour withing go versions.
See also golang/go#24588
This is a workaround for a change in behaviour between go <= 1.9 and go
1.10.
Prior to go 1.9, compiling a test would not fail if the specified
output dir does not exist. However, it does fail in go 1.10.
By failing when the the directory does not exist, we have a consistent
behaviour withing go versions.
See also golang/go#24588
alamages
pushed a commit
to alamages/ginkgo
that referenced
this issue
Apr 10, 2018
This is a workaround for a change in behaviour between go <= 1.9 and go
1.10.
Prior to go 1.9, compiling a test would not fail if the specified
output dir does not exist. However, it does fail in go 1.10.
By failing when the the directory does not exist, we have a consistent
behaviour withing go versions.
See also golang/go#24588
Description
go test
command fails when using the flag-c
, if-outpudir
is set to a non-existing directory.What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?GOARCH="amd64"
What did you do?
go test -c -cover -outputdir=./all/profiles/here -coverprofile=profile.txt
The command above does not report an error with go1.9.4.
What did you expect to see?
I would expect no error when compiling the test, but rather when running it (as it was prior to go1.10).
What did you see instead?
An error occurs:
The text was updated successfully, but these errors were encountered: