New issue
Advanced search Search tips

Issue 737594 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jan 10
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

thread_times.key_idle_power_cases failing on chromium.perf/Android One Perf

Project Member Reported by altimin@chromium.org, Jun 28 2017

Issue description

thread_times.key_idle_power_cases failing on chromium.perf/Android One Perf

Failures (https://chromium-swarm.appspot.com/task?id=3705e0a1f53d8e10&refresh=10&show_raw=1):
* animated-gif.html
* blank.html
* css-animation.html
* request-animation-frame.html
* set-timeout.html
* set-timeout.html (Long Idle)


Builders failed on: 
- Android One Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf



 
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, Jun 28 2017


=== BISECT JOB RESULTS ===
NO Test failure found

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : thread_times.key_idle_power_cases
  Metric       : benchmark_duration/benchmark_duration

Revision             Exit Code      N
chromium@481869      0 +- N/A       20      good
chromium@481986      0 +- N/A       20      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.key_idle_power_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8975531189211298592

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5097940655276032


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Project Member

Comment 3 by sheriffbot@chromium.org, Jun 29 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Archived (was: Untriaged)
Archiving issues with no priority, no component and no owner

Sign in to add a comment