Page MenuHomePhabricator

Fix a bug where the TeamCity build only reports one of the test_runner runs
ClosedPublic

Authored by jasonbcox on Jul 17 2019, 21:48.

Details

Summary

The junit output of each successive test_runner.py run overwrites junit_results.xml.
This leads to a build failure, but tests reporting as passed: https://build.bitcoinabc.org/viewLog.html?buildId=16488&buildTypeId=BitcoinABC_Master_BitcoinAbcMasterAsan&tab=buildResultsDiv
It also leads to incorrect test failure reporting, making it impossible to track flaky or spurious test failures.

This diff fixes that by writing each run to it's own output file.

Test Plan

See the TeamCity build for this diff: https://build.bitcoinabc.org/viewLog.html?buildId=16722&buildTypeId=BitcoinABC_BitcoinAbcStaging&tab=testsInfo
In the "View:" dropdown, select tests without grouping by name

Diff Detail

Repository
rABC Bitcoin ABC
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

jasonbcox edited the test plan for this revision. (Show Details)

ju is probably about the worse name possible.

contrib/teamcity/build.sh
90 ↗(On Diff #10340)

Why is there a cutoff on master ?

This revision is now accepted and ready to land.Jul 17 2019, 23:27
contrib/teamcity/build.sh
90 ↗(On Diff #10340)

There doesn't seem to be a rationale for it here: https://reviews.bitcoinabc.org/D1929 but it's clearly intended to run extended tests.