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

Issue 719631 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature
Launch-Exp-Leadership: NotReviewed
Launch-Leadership: NotReviewed

Blocking:
issue 697444



Sign in to add a comment

Doc(s) for how to change perf build configs, e.g. update OS version

Project Member Reported by benhenry@chromium.org, May 8 2017

Issue description

We break things when updating OS versions, like when we moved Mac OSX 10.9 to 10.11. There were some benchmarks that failed to continue running because we did this without updating the benchmark configs.
 
Blocking: 697444
Project Member

Comment 2 by sheriffbot@chromium.org, Aug 7 2017

This launch bug has not been modified in the last 90 days and has no milestone label. Please take a look and add appropriate milestone label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: martiniss@chromium.org
IS this related to Stephen and I's effort to document the process of updating/adding new hardware to the labs?
Project Member

Comment 4 by sheriffbot@chromium.org, Nov 6 2017

This launch bug has not been modified in the last 90 days and has no milestone label. Please take a look and add appropriate milestone label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 5 by sheriffbot@chromium.org, Feb 12 2018

This launch bug has not been modified in the last 90 days and has no milestone label. Please take a look and add appropriate milestone label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: -Speed>Benchmarks Speed>Benchmarks>Waterfall
Owner: eyaich@chromium.org
Putting this on Emily's backlog. Feel free to get back to this whenever you have more bandwidth :-)
Project Member

Comment 7 by sheriffbot@chromium.org, May 14 2018

This launch bug has not been modified in the last 90 days and has no milestone label. Please take a look and add appropriate milestone label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 8 by amin...@google.com, May 16 2018

Labels: Launch-Exp-Leadership-NotReviewed
Setting default state for new Launch-Exp-Leadership field per updates to go/newChromeFeature.  Ping amineer@ with questions.

Comment 9 by amin...@google.com, May 16 2018

Labels: Launch-Leadership-NotReviewed
Setting default state for new Launch-Leadership field per updates to go/newChromeFeature.  Ping amineer@ with questions.

Can anyone help me understand why this is marked as Type=Launch and requires cross-functional review?

Is anyone planning to do anything here?
Labels: -Type-Launch Type-Feature
This is on the backlog but it is more of a feature request for our documentation.  
Status: Assigned (was: Available)
Cc: sullivan@chromium.org
eyaich's last visit was >30 days ago. +sullivan to get a message through. Or if this is not important, to close the bug.
Owner: nednguyen@chromium.org
Ned, can you triage since Emily is out?
Owner: jbudorick@chromium.org
Some doc we wrote back then is in https://docs.google.com/document/d/1zfynNSYjN7cb0FgwwDx3igUkpGxitA-vedp77DQ2QNM/edit#heading=h.we6429s1n247

Reassign to John to drive this since he owns perf waterfall now
Components: -Speed>Release
Taking off Speed>Release label since that's used for regressions in chrome metrics.

Sign in to add a comment