go-bamboo-plugin
go-bamboo-plugin copied to clipboard
edwinakatosh
go test exits with non zero exit code, so test parser never runs when tests fail
I must be missing something - the go test task exits with non-zero when a test fails, this means the next task which is meant to be the test parser never runs, which means my tests don't get parsed and shown in the interface.
Is this by design, or have I done something horribly wrong in my setup somewhere?
Failing test - skips to running post build steps ...
build 12-Oct-2016 14:29:34 FAIL build 12-Oct-2016 14:29:34 exit status 1 build 12-Oct-2016 14:29:34 FAIL bitbucket.org/fusemail/fm-utility-golang-trackerdb 0.007s simple 12-Oct-2016 14:29:34 Failing task since return code of [/usr/local/go/bin/go test -v .] was 1 while expected 0 simple 12-Oct-2016 14:29:34 Finished task 'Test' with result: Failed simple 12-Oct-2016 14:29:34 Running post build plugin 'NCover Results Collector'
Successful test - runs the test parser ...
build 12-Oct-2016 14:26:36 --- PASS: TestBase62 (0.00s) build 12-Oct-2016 14:26:36 PASS build 12-Oct-2016 14:26:36 ok bitbucket.org/fusemail/fm-utility-golang-trackerdb 0.004s simple 12-Oct-2016 14:26:36 Finished task 'Test' with result: Success simple 12-Oct-2016 14:26:36 Starting task 'Parse Tests' of type 'com.handcraftedbits.bamboo.plugin.go:task.go.test.parser' simple 12-Oct-2016 14:26:36 Parsing test results under /var/lib/bamboo/xml-data/build-dir/GO-TRAC-JOB1... simple 12-Oct-2016 14:26:36 Finished task 'Parse Tests' with result: Success
I was able to workaround this by having the test results parser be a "Final Task." This will cause the parser to run even if the tests fail. I think this is how it was designed to work.
Happens to me as well, using Bamboo 6.3.0. My tests pass but go test returns a non zero code and the task fails because of that.
