commit | 3c50ac9c72edccca07ceba6f554b50c8057abf93 | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-roller@chromium.org> | Fri Jan 11 21:09:10 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Jan 11 21:09:10 2019 |
tree | 117317aaf3c0fcaf47a80d0c1c4692949b16530f | |
parent | 4d673d16886acaf47a8fa1a57e2709da69e37227 [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/c79a7556da9e8e45df3dc0a160d8dd304a2b25cf Revert "Support 'xcode parallelization' flag on the test blocks level." (jbudorick@chromium.org) recipe_engine: https://crrev.com/d7bf17e6450a8aef49e08d4dfcac10b2bb558b8d [arguments.proto] Regenerate pb2. (iannucci@chromium.org) TBR=iannucci@chromium.org Recipe-Tryjob-Bypass-Reason: Autoroller Bugdroid-Send-Email: False Change-Id: Ie7c6ca2b227ea40c8945bf0f6feef716e6e8171c Reviewed-on: https://chromium-review.googlesource.com/c/1407509 Reviewed-by: Recipe Roller <recipe-roller@chromium.org> Commit-Queue: Recipe Roller <recipe-roller@chromium.org> Cr-Commit-Position: refs/heads/master@{#19939} Cr-Mirrored-Commit: 865a2ce4731108ff3d158400add2d07249bd2e6e
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.