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

Issue 596172 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Dec 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

404 trying to view revision range between two builds

Project Member Reported by rsch...@chromium.org, Mar 18 2016

Issue description

https://chromium.googlesource.com/chromium/src/+log/50.0.2632.0..50.0.2634.0?pretty=fuller&n=10000

Getting a 404. Both builds exist, according to omahaproxy: https://omahaproxy.appspot.com/history

amineer suggested this could be a git tagging issue.
 

Comment 1 by mmoss@chromium.org, Mar 21 2016

Labels: -Infra-Git
Apparently 2634.0 tag doesn't exist:

https://chromium.googlesource.com/chromium/src/+/50.0.2634.0

Not sure why, but I'd guess some sort of failure in the nightly branching (although I'm not sure why it would be in omaha then).

[-Infra-git, since it's not an error with the repo, but an error in how we use the repo, i.e. failure to create the tag]

Labels: Needs-Feedback
@rschoen: Would you mind checking as per comment #1 ?

Appreciate your help.

Thank you!
Labels: -Needs-Feedback
I'm not sure what I'm supposed to check. mmoss said it seemed to be some sort of failure in the nightly branching.
Labels: Te-NeedsFurtherTriage
Cc: -amineer@chromium.org benhenry@chromium.org
benhenry@, this smells like an infra issue, but c#1 removed it from all infra queues.  Is that the right practice?  How do you suggest we route it?
Project Member

Comment 6 by sheriffbot@chromium.org, May 10 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: Infra>Git
Status: Untriaged (was: Archived)
This is still an issue. Moving to correct bucket. This is either a problem with Gitilies (the one throwing the 404) or our use of omahaproxy with the Gitiles REST API.
Status: Archived (was: Untriaged)
This is 2 years old and I don't see any other mentions of it so whatever caused this mismatch between git tags and omahaproxy... doesn't seem like a priority to investigate it now.

Sign in to add a comment