bisect started at https://chromeperf.appspot.com/buildbucket_job_status/9017382707778937952

+perezju for test owner

Randy, could you have a look?

Issue 597232 has been merged into this issue.

Note: Chrome is actually crashing

	I    1.430s Main  pid: 20932, tid: 20948, name: CrRendererMain  >>> org.chromium.chrome:sandboxed_process8                                       <<<
	I    1.430s Main  signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
	I    1.430s Main  [FATAL:safe_conversions.h(49)] Check failed: IsValueInRangeForNumericType<Dst>(value). 
	I    1.430s Main      r0 00000000  r1 000051d4  r2 00000006  r3 00000000
	I    1.430s Main      r4 afad9db8  r5 00000006  r6 00000016  r7 0000010c
	I    1.430s Main      r8 b6f9bdf4  r9 afad9314  sl 00000000  fp 953fd358
	I    1.430s Main      ip 000051d4  sp afad8e68  lr b6f45579  pc b6f694dc
	I    1.431s Main  
	I    1.431s Main  Stack Trace:
	I    1.431s Main    RELADDR   FUNCTION                 FILE:LINE
	I    1.431s Main    0003b4dc  tgkill+12                /system/lib/libc.so
	I    1.431s Main    00017575  pthread_kill+52          /system/lib/libc.so
	I    1.431s Main    00018187  raise+10                 /system/lib/libc.so
	I    1.431s Main    00014ae5  __libc_android_abort+36  /system/lib/libc.so
	I    1.431s Main    00012aac  abort+4                  /system/lib/libc.so
	I    1.431s Main    01ab345d  <unknown>                /data/app/org.chromium.chrome-1/lib/arm/libchrome_public.so
	I    1.431s Main  
	I    1.431s Main  -----------------------------------------------------
	I    1.431s Main  
	I    1.431s Main  signal 6 (SIGABRT), code -6 in tid 20948 (CrRendererMain)
	I    1.431s Main  
	I    1.431s Main  pid: 20932, tid: 20932, name: dboxed_process8  >>> org.chromium.chrome:sandboxed_process8                                       <<<
	I    1.431s Main      r0 fffffffc  r1 be9ece60  r2 00000010  r3 ffffffff
	I    1.431s Main      r4 00000000  r5 00000008  r6 00000000  r7 0000015a
	I    1.431s Main      r8 b4d52018  r9 00000014  sl 00000001  fp 12c85ca0
	I    1.431s Main      ip be9ece10  sp be9ece00  lr b6f430e5  pc b6f69638
	I    1.431s Main  
	I    1.431s Main  Stack Trace:
	I    1.431s Main    RELADDR   FUNCTION                                                 FILE:LINE
	I    1.431s Main    0003b638  __epoll_pwait+20                                         /system/lib/libc.so
	I    1.431s Main    000150e1  epoll_pwait+26                                           /system/lib/libc.so
	I    1.431s Main    000150ef  epoll_wait+6                                             /system/lib/libc.so
	I    1.431s Main    0001260b  android::Looper::pollInner(int)+98                       /system/lib/libutils.so
	I    1.431s Main    00012835  android::Looper::pollOnce(int, int*, int*, void**)+92    /system/lib/libutils.so
	I    1.431s Main    00087ed1  android::NativeMessageQueue::pollOnce(_JNIEnv*, int)+22  /system/lib/libandroid_runtime.so
	I    1.431s Main    000b23b7  <unknown>                                                /data/dalvik-cache/arm/system@framework@boot.oat
https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Galaxy%20S5%20Perf%20%281%29/builds/2013/steps/power.typical_10_mobile/logs/stdio

My first thought is that this is less likely to be related to the power test than it is to be related to the pageset. I'm not in the office today, but will try to reproduce locally tomorrow. I will look into seeing if any other tests use the same page set.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/70351e83fb03f7b02d62519410cf3001773c94b2

commit 70351e83fb03f7b02d62519410cf3001773c94b2
Author: zhenw <zhenw@chromium.org>
Date: Wed Mar 23 18:48:51 2016

Disable power.typical_10_mobile on Android Perf bots

BUG= 597290 
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:winx64_10_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq
TBR=nednguyen@google.com

Review URL: https://codereview.chromium.org/1830603002

Cr-Commit-Position: refs/heads/master@{#382890}

[modify] https://crrev.com/70351e83fb03f7b02d62519410cf3001773c94b2/tools/perf/benchmarks/power.py

The run before this landed passed, it may have been fixed already.

https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus5%20Perf%20%281%29/builds/2433

Maybe waiting a bit. I will revert the disable CL if the bisect result confirms.

The problem should be fixed by https://codereview.chromium.org/1822353002.

Reverting the disable now.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/b70595110a1fd24f7225e1d82fd7b92eb5cb2b6c

commit b70595110a1fd24f7225e1d82fd7b92eb5cb2b6c
Author: zhenw <zhenw@chromium.org>
Date: Wed Mar 23 20:54:40 2016

Revert of Disable power.typical_10_mobile on Android Perf bots (patchset #1 id:1 of https://codereview.chromium.org/1830603002/ )

Reason for revert:
The problem is fixed by https://codereview.chromium.org/1822353002

Original issue's description:
> Disable power.typical_10_mobile on Android Perf bots
>
> BUG= 597290 
> CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:winx64_10_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq
> TBR=nednguyen@google.com
>
> Committed: https://crrev.com/70351e83fb03f7b02d62519410cf3001773c94b2
> Cr-Commit-Position: refs/heads/master@{#382890}

TBR=
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG= 597290 

Review URL: https://codereview.chromium.org/1826003002

Cr-Commit-Position: refs/heads/master@{#382923}

[modify] https://crrev.com/b70595110a1fd24f7225e1d82fd7b92eb5cb2b6c/tools/perf/benchmarks/power.py

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Moving catapult revision to the vars dictionary in DEPS.
Author  : robertocn
Commit description:
  
This is necessary for auto-bisect to descend into catapult rolls.

R=nednguyen,sullivan
BUG= 596445 

Review URL: https://codereview.chromium.org/1820083003

Cr-Commit-Position: refs/heads/master@{#382784}
Commit  : 4567f4d81d97428183c2b78d2bfde53b18883c13
Date    : Wed Mar 23 03:37:19 2016


===== TESTED REVISIONS =====
Revision                Exit Code   Std. Dev.   Num Values  Good?
chromium@382773         1           N/A         5           good
chromium@382779         1           N/A         5           good
chromium@382782         1           N/A         5           good
chromium@382783         1           N/A         5           good
chromium@382784         1           N/A         5           bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 597290

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests power.typical_10_mobile
Test Metric: application_energy_consumption_mwh/http___siriuslymeg.tumblr.com_
Relative Change: 0.00%
Score: 0.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/548
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9017382707778937952


| 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 label Cr-Tests-AutoBisect.  Thank you!