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

Issue 817043 link

Starred by 3 users
Status: Fixed
Owner:
█ pras...@chromium.org
Last visit 26 days ago
Closed: Apr 2018
Cc:
█ amineer@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Chromium Dash Feedback - incorrect data for release?

Project Member Reported by scottmg@chromium.org, Feb 27 2018 
I tried entering "r456789" into go/find-releases, and it reports https://storage.googleapis.com/chromium-find-releases-static/247.html#2476b555727bb19508ae94feafa76dc6b9a69c1d

When I search for commit:2476b555727bb19508ae94feafa76dc6b9a69c1d in Chromium Dash I get this beautiful page https://chromiumdash.appspot.com/commit/2476b555727bb19508ae94feafa76dc6b9a69c1d. But it claims that CL (from 11 months ago) hasn't been released, whereas find-releases says it was in 59.0.3042.0.

Do you know why there's a discrepancy there?

Comment 1 by prasadv@google.com, Feb 27 2018

Status: Available (was: Unassigned)
The following are the version from where commits are updated with version information. We thought user might not be interested in checking data from  very old milestones. In your case the commit is from 59.0.3042.0, which was not processed.

Canary
Android: 65.0.3284.0
Mac: 65.0.3302.0
Windows: 65.0.3303.0

Dev
Android: 64.0.3281.0
Linux: 64.0.3278.0
Mac: 64.0.3278.0
Windows: 64.0.3282.14
iOS: 64.0.3260.0

Beta
Android: 63.0.3239.53
Linux: 63.0.3239.90
Mac: 63.0.3239.90
Windows: 63.0.3239.90
iOS: 63.0.3239.53

Stable
Android: 62.0.3202.84
Linux: 62.0.3202.94
Mac: 62.0.3202.94
Windows: 62.0.3202.94
iOS: 61.0.3163.73

Alex@ Do you think we should process very old milestones too?

Comment 2 by amineer@chromium.org, Mar 1 2018 

 Issue 817577  has been merged into this issue.

Comment 3 by amineer@chromium.org, Mar 26 2018 

 Issue 822288  has been merged into this issue.

Comment 4 by amineer@chromium.org, Mar 26 2018

Labels: -Pri-2 Pri-1
Owner: pras...@chromium.org
Status: Assigned (was: Available)
prasadv@, you were going to backfill all versions / channels / platforms back to the same point last week - did that occur?  If not, what's current status / plan?
Project Member

Comment 5 by bugdroid1@chromium.org, Mar 27 2018 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infra/infra_internal/+/fbffd1f2d296956342c465700f619bc39b3e0a9a

commit fbffd1f2d296956342c465700f619bc39b3e0a9a
Author: prasadv <prasadv@google.com>
Date: Tue Mar 27 23:12:47 2018
Project Member

Comment 6 by bugdroid1@chromium.org, Apr 2 2018 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infra/infra_internal/+/381738c36cd2d4f65fce1eee59c7b2a253cada6d

commit 381738c36cd2d4f65fce1eee59c7b2a253cada6d
Author: prasadv <prasadv@google.com>
Date: Mon Apr 02 17:27:35 2018

Comment 7 by amineer@chromium.org, Apr 2 2018

Status: Fixed (was: Assigned)
This now displays a more appropriate message - specifically, that data from commits landed prior to M61 aren't available in Chromium Dash.  We've also processed all commits from M61+.  So, everything should now be consistent.
►

Sign in to add a comment