commit | 54472fa9f5abba43d81a5db50be4a77c16902cae | [log] [tgz] |
---|---|---|
author | Andrii Shyshkalov <tandrii@chromium.org> | Sat Nov 18 02:59:56 2017 |
committer | Commit Bot <commit-bot@chromium.org> | Sat Nov 18 03:09:18 2017 |
tree | fe3deeb88dfa07edbce20d9ec94a4cc9b0e912e8 | |
parent | 9e02e223741b20c1493ac6d7521cd6b33d655da3 [diff] |
led: improvements in led get-build subcommand. 1. Support buildbucekt ID copied from MILO URL which has "b" prefix. Thus the following two commands are the same: $ led get-build b123 $ led get-build 123 2. ... and don't panic with nullptr deref if build=123 doesn't exist, but print error returned by buildbucket instead. R=iannucci@chromium.org Bug: Change-Id: I9e8482100f3091a2a45a5ac49b0c4f2bc418924a Reviewed-on: https://chromium-review.googlesource.com/777989 Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
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.