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

Issue 674366 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Mar 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

gsubtreed failing since 2016-12-02

Project Member Reported by dsansome@chromium.org, Dec 15 2016

Issue description

http://shortn/_XzXUmMcDOk

It seems to be failing for the following repos:
components/feedback
net/tools/testserver
third_party/sqlite
third_party/tcmalloc/chromium
third_party/zlib

With errors like:

[I2016-12-15T01:46:25.334480+00:00 24997 139695573817152 infra.services.gsubtreed.gsubtreed:154] processing Ref(Repo('https://chromium.googlesource.com/chromium/src'), 'refs/branch-heads/2357')
error: refs/heads/master does not point to a valid object!
To https://chromium.googlesource.com/a/chromium/src/third_party/zlib
 ! [rejected]                  79db2186a80dc306c3c0b0a400190d52446de8c7 -> master (fetch first)
error: failed to push some refs to 'https://chromium.googlesource.com/a/chromium/src/third_party/zlib'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

For each one of these I also notice a message:
[W2016-12-15T01:52:55.414197+00:00 24997 139695573817152 infra.services.gsubtreed.gsubtreed:198] path 'third_party/zlib' was deleted in commit Commit(Repo('https://chromium.googlesource.com/chromium/src'), '5d4451ebf298d9d71f716cc0135f465cec41fcd0')

Note that that commit was made in 2011: https://chromium.googlesource.com/chromium/src/+/5d4451ebf298d9d71f716cc0135f465cec41fcd0
 

Comment 1 by iannu...@google.com, Dec 15 2016

The warning you refer to is irrelevant.

For some reason the hash it's trying to push to the subtree mirror doesn't match what's already there (though the subtree mirror looks fully populated to me), at least for zlib.

Comment 2 by iannu...@google.com, Dec 17 2016

getting back to this, I'm going to take a look and see if I can see what changed
Status: Fixed (was: Assigned)
I did actually fix it, but didn't close the bug. It's currently happy.

Sign in to add a comment