aboutsummaryrefslogtreecommitdiff
path: root/produce_output.py
diff options
context:
space:
mode:
authorcmtice <cmtice@google.com>2014-04-02 14:11:39 -0700
committerchrome-internal-fetch <chrome-internal-fetch@google.com>2014-04-04 20:26:55 +0000
commit44a44befd1f500b9a227ebfd849702efce83ef6a (patch)
tree4f334cfad1a0433fed595729c0c57eeb2aed0864 /produce_output.py
parent841f96b7f89dbe6f3e5bb013d211a6f799e4d3ab (diff)
downloadtoolchain-utils-44a44befd1f500b9a227ebfd849702efce83ef6a.tar.gz
Check for 'significant' results at report generation instead of caching.
The current implementation of the option that masks unimportant results discards the uninteresting results before caching the test results. After further thought, that was not the right design choice. Among other things it can cause confusing results, such as seen in issue 357346. We should always cache all the results, and do the result filtering during report generation. This CL makes that change. BUG=357346,357343 TEST=Ran crosperf tests with and without cache hits, and with and without entreies in the json file. It all seems to work as expected. Change-Id: I778e5614c73bf751ebaa2d4606af636275247c60 Reviewed-on: https://chrome-internal-review.googlesource.com/159108 Reviewed-by: Yunlian Jiang <yunlian@google.com> Commit-Queue: Caroline Tice <cmtice@google.com> Tested-by: Caroline Tice <cmtice@google.com>
Diffstat (limited to 'produce_output.py')
0 files changed, 0 insertions, 0 deletions