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

Issue 741105 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug

Blocking:
issue 583731



Sign in to add a comment

Subtree repo falling out of sync

Project Member Reported by paulir...@chromium.org, Jul 11 2017

Issue description

For the past 3 hours or so, it appears that the devtools subtree repo (https://chromium.googlesource.com/chromium/src/third_party/WebKit/Source/devtools/) has fallen out of sync with Chromium git repo.

See attached screenshot comparing the log of the two repos. Note the bd74faa that's at the top of the Chromium repo. While it landed 3 hours ago, it hasn't appeared yet in the subtree one.

We have tooling downstream that expects these two repos to be in sync and breaks our builds if they're not.. Should we expect latencies like this, or is it unexpected to you as well? :)

Thank you!
 
Screen Shot 2017-07-11 at 2.32.29 PM.png
689 KB View Download

Comment 2 by aga...@chromium.org, Sep 15 2017

Blocking: 583731
Cc: iannucci@chromium.org
Components: -Infra>Git Infra>Git>Admin
Labels: -Pri-2 Infra-Troopers Pri-1
Status: Available (was: Untriaged)
The kind of latency reported here is not good and not expected. Gsubtreed is supposed to run every 10 minutes and have that be that.

I looks like it is... unhealthy. And may have been for a very long time.

https://uberchromegw.corp.google.com/i/chromium.infra.cron/builders/gsubtreed?numbuilds=200

Someone needs to dig in and figure out what's going wrong and fix it.
Owner: jchin...@chromium.org
Status: Started (was: Available)
Builder seems to be doing fine now. Paul, can you confirm that the sync'ing is no longer an issue? Thanks!
Hm, builder started failing again after a day. Looking into it.
Status: Fixed (was: Started)
It seems the builder generally failing is an instance of crbug/487002. The specific repos should be sync'd though, so I'll mark this as fixed.
I haven't been able to confirm this (as I have to wait for a commit to land).
But I'll assume its good and reopen if I spot an issue again.

Thanks for taking a look!
Sure thing. Thanks!

Sign in to add a comment