New issue
Advanced search Search tips

Issue 798379 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

12% regression in benchmark duration at 503957:504455

Project Member Reported by perezju@google.com, Jan 2 2018

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=798379

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=a50f62bb89675d490b49c4b54172fb4de21a391ef331dad1ba1a1ab64fe1051b


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

linux-release
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/12ccbe03040000
Cc: dtu@chromium.org
+dtu is this kind of bisect (on benchmark duration) already supported by pinpoint?

Not sure why all builds return with: "ReadValueError: The test didn't produce chartjson-output.json."

Comment 5 by dtu@chromium.org, Jan 3 2018

I think it should work. Filed https://github.com/catapult-project/catapult/issues/4141 for the failure.
Cc: nedngu...@google.com
+nednguyen I noticed this spike on benchmark duration on several benchmarks, are you aware of anything that could have caused it?

Comment 7 by benhenry@google.com, Jan 16 (6 days ago)

Components: Test>Telemetry

Comment 8 by benhenry@google.com, Jan 16 (6 days ago)

Components: -Speed>Telemetry

Sign in to add a comment