commit | c4df85cd48077f2aca459627979eb3a5a0a7e1c1 | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-roller@chromium.org> | Wed Feb 20 03:56:43 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Feb 20 03:56:43 2019 |
tree | 9da75e3e055b2919c6b36cf9450e9df72e26d12e | |
parent | 3c5e7cc07304f84ba5a35af3f7f0b066352d8f35 [diff] |
Roll recipe dependencies (trivial). This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (e.g. depot_tools) into downstream projects (e.g. tools/build). More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. build: https://crrev.com/6e017afb8033360e475733e4c1b0c4ff660efa86 Define header guards to hack around Kythe using CUDA's wrapper headers. (jsca@google.com) depot_tools: https://crrev.com/0e617c02945fa5ee56983bdbe6d6820ab62baf29 Change git cl comments to list robot comments. (qyearsley@chromium.org) recipe_engine: https://crrev.com/0b76adbaaf0c63208748ddce760c73205424155f [buildbucket] Add api.buildbucket.run (nodir@google.com) https://crrev.com/658ffc6b4e0f12ab1b7310ef662acffcf23770ca Add an assertions recipe module for unit tests. (gbeaty@chromium.org) TBR=iannucci@chromium.org Recipe-Tryjob-Bypass-Reason: Autoroller Bugdroid-Send-Email: False Change-Id: I54629be3a5d0c40123b40febeb8b7ad2c55dc88b Reviewed-on: https://chromium-review.googlesource.com/c/1478412 Reviewed-by: Recipe Roller <recipe-roller@chromium.org> Commit-Queue: Recipe Roller <recipe-roller@chromium.org> Cr-Commit-Position: refs/heads/master@{#20772}
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.