Skip to content

Commit

Permalink
Clarify unit test failures on windows (#7741)
Browse files Browse the repository at this point in the history
When these tests fail it is important that users look not in the log, but in the
test report interface, or the test output artifact for further info.
  • Loading branch information
andrewvc authored and ruflin committed Jul 26, 2018
1 parent bb4adc0 commit 2df93d0
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion dev-tools/jenkins_ci.ps1
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ exec { mage build } "Build FAILURE"

echo "Unit testing $env:beat"
go test -v $(go list ./... | select-string -Pattern "vendor" -NotMatch) 2>&1 | Out-File -encoding UTF8 build/TEST-go-unit.out
exec { Get-Content build/TEST-go-unit.out | go-junit-report.exe -set-exit-code | Out-File -encoding UTF8 build/TEST-go-unit.xml } "Unit test FAILURE"
exec { Get-Content build/TEST-go-unit.out | go-junit-report.exe -set-exit-code | Out-File -encoding UTF8 build/TEST-go-unit.xml } "Unit test FAILURE, view testReport or TEST-go-unit.out jenkins artifact for detailed error info."

echo "System testing $env:beat"
# Get a CSV list of package names.
Expand Down

0 comments on commit 2df93d0

Please sign in to comment.