From 2df93d0a24d602e0835190cfd87863188567ed8d Mon Sep 17 00:00:00 2001 From: Andrew Cholakian Date: Thu, 26 Jul 2018 01:54:03 -0500 Subject: [PATCH] Clarify unit test failures on windows (#7741) 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. --- dev-tools/jenkins_ci.ps1 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dev-tools/jenkins_ci.ps1 b/dev-tools/jenkins_ci.ps1 index a8a0c8e96ff7..efb5d4187ffa 100755 --- a/dev-tools/jenkins_ci.ps1 +++ b/dev-tools/jenkins_ci.ps1 @@ -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.