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

Issue 843465 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Aug 6
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

canary release information updated late?

Project Member Reported by neis@chromium.org, May 16 2018

Issue description

I'd like to rely on ChromiumDash when checking if a commit has already made it into a canary, but it seems that the information is not always up to date.  For instance, https://chromiumdash.appspot.com/commit/1825cccf5efe4b1020bda1ed1c285df93de66b18 currently says my commit hasn't been released yet, but in fact it's in the latest canary (68.0.3432.0).
 

Comment 1 by amin...@google.com, May 18 2018

Question: when you looked at the page, what platform did you select up top - Windows, or Android?

Since Android releases later, it's possible that the change was listed as shipped for Windows but wasn't actually released for Android, hence it not showing up.  We have some plans to fix this if that's the case, as we'll likely show all platforms rather than making you chose (which should alleviate this).

Let me know and we can go from there.  Thanks for the report!

Comment 2 by neis@chromium.org, May 23 2018

I don't remember, but I'll check with one of the next commits and let you know. Thanks.
Owner: neis@chromium.org
Status: Assigned (was: Unassigned)
 neis@, Is this still an issue? Were you able to verify commit release info, I'm assigning this to you, please feel free to assign it back.
Status: WontFix (was: Assigned)
I haven't experienced the issue since then. Perhaps it really was the platform selection, as mentioned in #1.

Sign in to add a comment