404 trying to view revision range between two builds |
||||||||
Issue descriptionhttps://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.
,
Apr 1 2016
@rschoen: Would you mind checking as per comment #1 ? Appreciate your help. Thank you!
,
Apr 1 2016
I'm not sure what I'm supposed to check. mmoss said it seemed to be some sort of failure in the nightly branching.
,
May 9 2016
,
May 9 2016
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?
,
May 10 2017
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
,
May 10 2017
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.
,
Dec 13
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 |
||||||||
Comment 1 by mmoss@chromium.org
, Mar 21 2016