Canary Delivery Issue: #62.0.3195.0 Daily job failed in http://chromepmo.appspot.com/trigger page |
||
Issue descriptionCanary trigger date/time: Aug. 23, 2017, 8:04 p.m. Version: 62.0.3195.0 OS: All Trigger & branch.py stage : Canary # 62.0.3194.0 not triggered and showing the 'Failed steps failed validate_version.read_version_for_3195 failed generate_buildspec.fetch .deps.git' in http://chromepmo.appspot.com/trigger page. Builder URL: ---------------- https://uberchromegw.corp.google.com/i/official.infra.cron/builders/chrome-branch/builds/189 Error Log URL: ------------------- https://uberchromegw.corp.google.com/i/official.infra.cron/builders/chrome-branch/builds/189/steps/update_trunk_version.git%20cl%20upload/logs/stdio Error Log: ------------- chrome/VERSION | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) error: remote unpack failed: error Missing unknown 4a74c2eb4b0c25316d75d3693a6479bdd761ba7f To https://chromium.googlesource.com/a/chromium/src.git ! [remote rejected] 1f2758ece27a9510852abd8ea33e03ea2abe7b5e -> refs/for/refs/heads/master%ready,notify=ALL,m=Initial_upload (n/a (unpacker error)) error: failed to push some refs to 'https://chromium.googlesource.com/a/chromium/src.git' Error after CL description prompt -- saving description to /home/chrome-bot/.git_cl_description_backup Failed to create a change. Please examine output above for the reason of the failure. Hint: run command below to diagnose common Git/Gerrit credential problems: git cl creds-check step returned non-zero exit code: 1 @@@STEP_LOG_LINE@stdout@Ack chromepmo.appspot.com with params: {'builder_url': 'https://uberchromegw.corp.google.com/i/official.infra.cron/builders/chrome-branch/builds/189', 'key': 'ag9zfmNocm9tZXBtby1ocmRyFAsSB0NvbW1hbmQYgICA8Li-nwoM', 'stdout': ''}@@@ @@@STEP_LINK@logdog-->stdout@https://luci-logdog.appspot.com/v/?s=infra-internal%2Fbb%2Fofficial.infra.cron%2Fchrome-branch%2F189%2F%2B%2Frecipes%2Fsteps%2Fupdate_trunk_version%2F0%2Fsteps%2Fgit_cl_upload%2F0%2Flogs%2Fstdout%2F0@@@ Michael, could you please look into this and help.
,
Aug 24 2017
This appears to have just been a hiccup with the git server. Do you want to trigger another one, or won't there be enough time because of the golo maintenance?
,
Aug 24 2017
I've already triggered another build as we need it for Android. Should we repurpose this bug to discuss perhaps auto-retriggering in cases like this, or simply close it?
,
Aug 24 2017
Actually, I don't think we can just retrigger, since it did already create the 3195 branches, and then failed later (basically at the very end) of the process (note that your retrigger failed). I think we need to manually bump the VERSION file to 3195, to match the branches it already created, then wait a little while for that change to work its way through the buildbots, and then branch again, at what will be 3196.
,
Aug 24 2017
Make it so, please.
,
Aug 24 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b2fbea12e27ac2fca470df1c2d95c49f7e54cfeb commit b2fbea12e27ac2fca470df1c2d95c49f7e54cfeb Author: Michael Moss <mmoss@google.com> Date: Thu Aug 24 18:30:48 2017 Manually updating trunk VERSION from 3195.0 to 3196.0 Last night's canary branching failed when committing the VERSION bump, so it needs to be manually brought back in sync. Also add more OWNERS to support any future reviews. BUG= 758465 R=amineer@chromium.org, govind@chromium.org Change-Id: Ief9754314a8cf026e800398369e384f43ffb4dee Reviewed-on: https://chromium-review.googlesource.com/633423 Reviewed-by: Nico Weber <thakis@chromium.org> Reviewed-by: Krishna Govind <govind@chromium.org> Commit-Queue: Michael Moss <mmoss@chromium.org> Cr-Commit-Position: refs/heads/master@{#497130} [modify] https://crrev.com/b2fbea12e27ac2fca470df1c2d95c49f7e54cfeb/chrome/OWNERS [modify] https://crrev.com/b2fbea12e27ac2fca470df1c2d95c49f7e54cfeb/chrome/VERSION
,
Aug 24 2017
VERSION file should be fixed, but now there's definitely not enough time to start a build before the golo maintenance, but after that should be good, if we still want one before the normal nightly.
,
Aug 24 2017
Thank you Michael, will just wait for tonight's canary.
,
Aug 24 2017
,
Aug 24 2017
FWIW, looks like that "unpack" error was happening a bunch yesterday, as mentioned in Issue 757937 .
,
Aug 25 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chrome/tools/release/scripts/+/72cc53e03870964ff4918ef84637ef3df74b1898 commit 72cc53e03870964ff4918ef84637ef3df74b1898 Author: Michael Moss <mmoss@google.com> Date: Fri Aug 25 01:18:46 2017 |
||
►
Sign in to add a comment |
||
Comment 1 by gov...@chromium.org
, Aug 24 2017Labels: ReleaseBlock-Dev