commit | de751beff461c1bcf9a86d90e0d1f9b6bfab78a8 | [log] [tgz] |
---|---|---|
author | Sean McCullough <seanmccullough@chromium.org> | Wed Apr 17 18:16:59 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Apr 17 18:16:59 2019 |
tree | 4aeef73cff68bbdab88391101f3fc7d3c5b01378 | |
parent | 20982a1665271ce1218eefd8d075362d2e458ca1 [diff] |
[som] fix chromium.perf test step analyzer Someone somewhere (?) changed a step name from "swarming.summary" to "chromium_swarming.summary" at some point, and that broke the analyzer's assumption about step names. So it just skipped that part of the test result analysis for chromium.perf and assumed there were no identifiable test results for the step. Bug: 943118 Change-Id: If11001309048f503387d16af1ff2a8814157ceb8 Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/1572084 Commit-Queue: Sean McCullough <seanmccullough@chromium.org> Reviewed-by: Aaron Gable <agable@chromium.org> Reviewed-by: Stephen Martinis <martiniss@chromium.org> Cr-Commit-Position: refs/heads/master@{#22451}
Welcome to the Chrome Infra repository!
Wondering where to start? Check out General Chrome Infrastructure documentation. In particular, to check out this repo and the rest of the infrastructure code, follow the instructions here. The rest of this page is specific to this repo.
sys.path
modifications.from infra.path_hacks.common import <stg>
is actually getting <stg>
from build/scripts/common.git push origin <updated hash>:deployed
git push
commandIf you've added a new module, integrate your tests with test.py:
Double-check that your tests are getting picked up when you want them to be: ./test.py test <path-to-package>
.
Tests still not getting picked up by test.py? Double-check to make sure you have init.py files in each directory of your module so Python recognizes it as a package.