New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 703268 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Apr 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Chrome OS R58 release branch is not updating Chrome correctly

Project Member Reported by bhthompson@google.com, Mar 20 2017

Issue description

Starting roughly last Tuesday we stopped getting Chrome uprevs on the 58 release branch.

The last successful one was https://uberchromegw.corp.google.com/i/chromeos_release/builders/samus-pre-flight-branch%20release-R58-9334.B/builds/39

I don't see anything in the change logs that is obvious, nothing special in Chromite for Chrome uprevving.

The root cause looks like we are not detecting new versions of Chrome.

"
21:12:10: INFO: RunCommand: cros_sdk -- ../../chromite/bin/cros_mark_chrome_as_stable '--tracking_branch=release-R58-9334.B' '--boards=samus' stable_release in /b/cbuild/shared_internal/src/scripts
 * Generating locale-archive: forcing # of jobs to 1
21:12:13: INFO: Stable candidate found /home/chrome-bot/trunk/src/third_party/chromiumos-overlay/chromeos-base/chromeos-chrome/chromeos-chrome-58.0.3029.19_rc-r1.ebuild
21:12:13: INFO: Previous ebuild with same version found and ebuild is redundant.
21:12:14: INFO: Found nothing to rev.
"

This seems to imply that it only finds 58.0.3029.19 at https://chromium.googlesource.com/chromium/src.git/+refs however I am seeing newer versions, this assumes we have the default URL here (have not traced that down yet).

I guess we may need to instrument more in the code?
 
Cc: steve...@chromium.org dimu@chromium.org
dimu@, Was there any recent change in the way Chrome is triggered/publishes DEPS?
With help from Josafat it looks like this is rooted in missing 'buildspec_platforms' from the DEPS file.

https://chromium.googlesource.com/chromium/src.git/+/58.0.3029.28/DEPS has no buildspec_platforms
but https://chromium.googlesource.com/chromium/src.git/+/58.0.3029.19/DEPS did.

So this is probably something on the Chrome triggering side.
Owner: amineer@chromium.org
+amineer as per our chat

Here is the bug I mentioned, please feel free to forward to the right owner to evaluate if buildpec_platform was deprecated in the DEPS

Comment 4 by dimu@google.com, Mar 20 2017

I'm taking a look.

Comment 5 by dimu@google.com, Mar 20 2017

Cc: -akes...@chromium.org amineer@chromium.org
Owner: dimu@chromium.org
Status: Started (was: Untriaged)

Comment 6 by dimu@google.com, Mar 20 2017

Cc: akes...@chromium.org
Cc: bhthompson@chromium.org
To try to unblock 58 for CrOS should we manually trigger a Chrome build on this branch with chrome os with force?

It would be good if we could get this done overnight, as ARC++ is broken on the branch until we can get a Chrome rev and that might be hiding other gremlins.

Comment 8 by dimu@google.com, Mar 20 2017

I'm triggering a ChromeOS build for 3029 branch now.
Project Member

Comment 9 by bugdroid1@chromium.org, Mar 21 2017

Project Member

Comment 10 by bugdroid1@chromium.org, Mar 22 2017

Labels: merge-merged-test
The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/release/scripts/+/bbd6d2ea9d67575da603bb53737a89a0b8190644

commit bbd6d2ea9d67575da603bb53737a89a0b8190644
Author: dimu <dimu@google.com>
Date: Wed Mar 22 21:39:25 2017

Comment 11 by dimu@chromium.org, Apr 19 2017

Is it still an issue? All public DEPS should have 'buildspec_platforms' entry now.
Status: Verified (was: Started)
Everything has been working smoothly, thanks!

Sign in to add a comment