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

Issue 817505 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
█ amineer@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Chromium Dash Feedback - commits page didn't show "first release" for merges to branch (flaky?)

Project Member Reported by mattm@chromium.org, Feb 28 2018 
The "commits" page didn't show "first release" for merges to a branch. 

I tried reloading the commits page, and then the first release was shown for the merges. (Oh, I had also signed in between the first load and the reload, dunno if that matters.)

If I click to the detailed commit info, it does show it there too.
chromiumdashcommits1.png
289 KB View Download

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

Status: WontFix (was: Unassigned)
I can repro the blank items if I swap the platform selector from Android to Windows and then back again, so my guess is that you had changed the platform to Windows, saw the blank items, reloaded (which swapped platform back to Android since that's the default) and then saw them show up.

We already have a bug for making preferred platform sticky ( issue 761763 ) which will help with the platform weirdness.  The commits don't have a "first release" for Windows because we probably didn't process the version they deployed in (see here for details on what we loaded: https://bugs.chromium.org/p/chromium/issues/detail?id=817043) - this will be an issue for older commits but shouldn't ever affect commits in the future.

Thus given this is a combo of two failures, I'm going to mark this as WontFix.  That said if you have questions, or you think a different approach is warranted, please re-open.

Thanks for the feedback, appreciate it!
►

Sign in to add a comment