diff options
| author | Stefan Zager <szager@chromium.org> | 2013-09-26 15:16:42 -0700 |
|---|---|---|
| committer | chrome-internal-fetch <chrome-internal-fetch@google.com> | 2013-09-27 20:45:29 +0000 |
| commit | d810e51da2145145247d52e7284afdf82dac74ac (patch) | |
| tree | 25bb93122cbf6eb42e757106a940b24e2ffdbab6 /scripts/cros_mark_as_stable.py | |
| parent | 895aa825fcabfe399858a22b041b56ce42d21582 (diff) | |
| download | chromite-d810e51da2145145247d52e7284afdf82dac74ac.tar.gz | |
Make sure the patch branch is checked out in patch.Apply().
Here's the problematic scenario:
- There's an existing working dir, and the patch branch is not
checked out.
- PatchSeries.Apply() is run.
- The first patch does not apply cleanly and is rolled back.
When the next patch enters GitRepoPatch.Apply(), the patch branch
will exist, but it won't be checked out. This doesn't happen
routinely in the CQ, because the CQ starts with the patch branch
checked out.
BUG=None
TEST=New validation_pool_unittest.py (under development)
Change-Id: I5a897be8689cf444bd7d7e08f5726b6e414a243c
Reviewed-on: https://chromium-review.googlesource.com/170831
Commit-Queue: Stefan Zager <szager@chromium.org>
Tested-by: Stefan Zager <szager@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Diffstat (limited to 'scripts/cros_mark_as_stable.py')
0 files changed, 0 insertions, 0 deletions