| 4bf85d17e38c3f36f64c761a0743591d296f41a5 |
|
23-Sep-2016 |
George Burgess IV <gbiv@google.com> |
[crosperf] Make generate_report report actual failures.
We would never increment `num_success`, so we'd always return failure.
This passed tests, since there were no tests that checked for success.
Also, testRunActionsRunsAllActionsRegardlessOfExceptions wasn't
really doing what it was supposed to; exceptions wouldn't get raised
(since the mocked WriteFile turns into a nop), so all of the WriteFile
actions were "passing". Because of the aforementioned bug, this test
seemed to work, as well.
BUG=None
TEST=generate_report_unittest.py passes; cros lint is happy.
Change-Id: If4d71af3415d97be8d5ac3bec796fe4589d50aaa
Reviewed-on: https://chrome-internal-review.googlesource.com/289802
Commit-Ready: George Burgess <gbiv@google.com>
Tested-by: George Burgess <gbiv@google.com>
Reviewed-by: Caroline Tice <cmtice@google.com>
/external/toolchain-utils/crosperf/generate_report.py
|
| c9df56c133c35bb5154a6c947d0986c35097c6e1 |
|
08-Sep-2016 |
George Burgess IV <gbiv@chromium.org> |
crosperf: Add generate_report.py.
This script allows us to generate HTML, JSON, text, and email reports
for JSON inputs, rather than needing to run things through crosperf.
BUG=chromium:641098
TEST=cros lint on new files passes, ./run_tests.sh passes.
Change-Id: I213149c0feca8b97f72fb447030c670e2f631a87
Reviewed-on: https://chrome-internal-review.googlesource.com/285238
Commit-Ready: George Burgess <gbiv@google.com>
Tested-by: George Burgess <gbiv@google.com>
Reviewed-by: Caroline Tice <cmtice@google.com>
/external/toolchain-utils/crosperf/generate_report.py
|