Closed bac closed 8 years ago
We are using go2xunit in a Jenkins environment with the call structure as suggested in the README.
I recently discovered this output in the console for a run that passed:
internal/charmstore/migrations_dump_test.go:27:2: cannot find package "gopkg.in/tomb.v2" in any of: /usr/lib/go/src/gopkg.in/tomb.v2 (from $GOROOT) /tmp/build/1830/src/gopkg.in/tomb.v2 (from $GOPATH) FAIL gopkg.in/juju/charmstore.v5-unstable/internal/charmstore [setup failed]
When the output was fed to go2xunit it did not recognize the setup failure and marked the run as a success, even though some tests did not even build.
go2xunit should look for setup failures and fail appropriately if -fail is passed.
Moved to bitbucket.
bac
commented
8 years ago bac
commented
8 years ago
We are using go2xunit in a Jenkins environment with the call structure as suggested in the README.
I recently discovered this output in the console for a run that passed:
When the output was fed to go2xunit it did not recognize the setup failure and marked the run as a success, even though some tests did not even build.
go2xunit should look for setup failures and fail appropriately if -fail is passed.