all release builders are submitting to manifest-versions |
||
Issue descriptionEvery single canary release builder is submitting changes to manifest-versions. https://chrome-internal-review.googlesource.com/chromeos/manifest-internal&usg=AFQjCNEIClkcBQhcrb6UHLtPWbDViq7v4w Example change: commit 7f06914e9b1e4d5d40f17632e4e9479bd4c17afc (HEAD -> master, origin/master, origin/HEAD) Author: chrome-bot <chrome-bot@chromium.org> Date: Mon Oct 9 16:54:25 2017 -0700 Automatic checkin: status=fail build_version 10017.0.0 for butterfly-release The diff for that change: diff --git a/build-name/butterfly-release/fail/63/10017.0.0.xml b/build-name/butterfly-release/fail/63/10017.0.0.xml new file mode 120000 index 0000000000..e04c5f02df --- /dev/null +++ b/build-name/butterfly-release/fail/63/10017.0.0.xml @@ -0,0 +1 @@ +../../../../buildspecs/63/10017.0.0.xml \ No newline at end of file This creates a symlink in: build-name/butterfly-release/fail/63/10017.0.0.xml That points at the pinned manifest created by the master builder.
,
May 31 2018
Hi, this bug has not been updated recently and remains untriaged. Please acknowledge the bug and provide status within two weeks (6/8/2018), or the bug will be closed. Thank you.
,
Jun 8 2018
Archiving per #2 |
||
►
Sign in to add a comment |
||
Comment 1 by dgarr...@chromium.org
, Oct 10 2017