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
{{ message }}
This repository has been archived by the owner on May 7, 2021. It is now read-only.
If a package contains only tests (ie all files end in _test.go), go-plus does not correctly run tests on save. While this isn't super common, you occasionally run into packages like this for integration tests.
The reason this doesn't work is because our save event handler runs go build prior to go test, and doesn't run tests if go build fails. It looks like go build returns a non-zero exit code in this case, which looks just like a compiler error.
We could detect this case by looking at go build's stderr and searching for no non-test Go files in.
The text was updated successfully, but these errors were encountered:
If a package contains only tests (ie all files end in _test.go), go-plus does not correctly run tests on save. While this isn't super common, you occasionally run into packages like this for integration tests.
The reason this doesn't work is because our save event handler runs
go build
prior togo test
, and doesn't run tests ifgo build
fails. It looks likego build
returns a non-zero exit code in this case, which looks just like a compiler error.We could detect this case by looking at
go build
's stderr and searching forno non-test Go files in
.The text was updated successfully, but these errors were encountered: