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

Issue 625113 link

Starred by 1 user
Status: WontFix
Owner:
█ philipel@chromium.org
Last visit > 30 days ago
Closed: Jul 2016
Cc:
█ phoglund@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

50% improvement in browser_tests at 402473:403005

Project Member Reported by philipel@chromium.org, Jul 1 2016 
See the link to graphs below.

Comment 1 by philipel@chromium.org, Jul 1 2016 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=625113

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgkrm0owkM


Bot(s) for this bug's original alert(s):

chromium-webrtc-rel-7
Project Member

Comment 2 by sheriffbot@chromium.org, Jul 1 2016

Labels: -M-53 M-54 MovedFrom-53
Moving this nonessential bug to the next milestone.

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

Comment 3 by philipel@chromium.org, Jul 4 2016

Cc: phoglund@chromium.org
Change in buildbot, from build130-a1 to build99-b1.

Still, a large change in the metrics. Were the old bots really old or something?

Comment 4 by phoglund@chromium.org, Jul 5 2016

Status: WontFix (was: Assigned)
Don't know. I don't like the 15%-with-zero-variance on the top bot, but the others look reasonable. This is as expected.
►

Sign in to add a comment