Revision ranges are incorrect |
|||||||
Issue descriptionhttps://screenshot.googleplex.com/a4FnQEyNqAm is an example For some reason SOM puts the incorrect revision ranges in it. I tried downloading the json, and deleting all alerts but that one. In that case, it correctly gives me the revisions. So something very strange is happening here.
,
Dec 13 2016
,
Jan 18 2017
If this is really a Pri-1, find an owner and update the priority. This is the result of a bulk edit that moved high priority available bugs to a lower priority in an attempt to be more honest with bug filers.
,
Aug 9 2017
Issue 708123 has been merged into this issue.
,
Aug 29 2017
Issue 758760 has been merged into this issue.
,
Aug 29 2017
This has been reported 5 times by users now. I am upping the priority to 1. Also, I think a good start to diagnosing this would be to make the revision range commits display numbers instead of hashes, so that it's easier to see if they are correct or not. Another thing that makes this super painful to debug is that on local Sheriff-o-Matic, CORS errors prevent the revision ranges from displaying at all. :/
,
Dec 14 2017
,
Jan 9 2018
This code now displays commit positions instead of hashes. Is this problem still happening?
,
Feb 15 2018
,
Feb 16 2018
Checking right now, I believe this is no longer happening and hasn't been reported in a long time. Feel free to reopen/file again if you see this again.
,
Dec 18
Issue 763511 has been merged into this issue. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by martiniss@chromium.org
, Dec 13 201684.5 KB
84.5 KB View Download