Issue metadata
Sign in to add a comment
|
v8.runtimestats.browsing_mobile_classic failing on Android Nexus5 Perf |
||||||||||||||||||||||
Issue descriptionA crash is happening during the test. However, the symbolize breakpad crashes seems to be unable to helpfully symbolize the microdump... https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_Nexus5_Perf__1_%2F5466%2F%2B%2Frecipes%2Fsteps%2Fsymbolized_breakpad_crashes%2F0%2Fstdout Going to try bisecting.
,
Mar 30 2017
This crash is also effecting the Nexus6 bot. Going to trigger a bisect on that bot as well.
,
Mar 30 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983677846159390256
,
Mar 31 2017
=== BISECT JOB RESULTS === Test failure found but unable to narrow commit range Build failures prevented the bisect from narrowing the range further. Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : v8.runtimestats.browsing_mobile_classic Metric : API:count_avg/browse_media Suspected Commit Range 40 commits in range https://chromium.googlesource.com/chromium/src/+log/65adef848f642a861ff781e24f8aaee11607698e..78ee69fc28e1b5f64bde754fc827f79582acc25e Revision Exit Code N chromium@460683 0 +- N/A 20 good chromium@460684 --- --- build failure --- --- --- too many build failures to list chromium@460722 --- --- build failure chromium@460723 1 +- 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 --story-filter=browse:media:youtube v8.runtimestats.browsing_mobile_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983677846159390256 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4584833625358336 | 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!
,
Mar 31 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: INFRA_FAILURE The bisect was able to narrow the range, you can try running with: good_revision: e8cf8925a1f9bf3fc2b428b56e8565ef2c008c3a bad_revision : 15bd8b5cbe93ed44c92b4108ef561ac278b91490 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : v8.runtimestats.browsing_mobile_classic Metric : API:count_avg/browse_media Revision Exit Code N chromium@460670 0 +- N/A 10 good chromium@460691 0 +- N/A 10 good chromium@460701 0 +- N/A 10 good chromium@460706 1 +- N/A 10 bad chromium@460711 1 +- N/A 10 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 v8.runtimestats.browsing_mobile_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983679068119204880 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4643422616420352 | 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!
,
Mar 31 2017
This failure was almost definitely caused by... https://codereview.chromium.org/2782413002 which was reverted due to it also causing failure on system health test.
,
Mar 31 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983573811411033792
,
Apr 2 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: INFRA_FAILURE The bisect was able to narrow the range, you can try running with: good_revision: 59b48ec0a88a1716bd4b39b2ac2d3021458749f4 bad_revision : 71d48fc435422a491d57bee6f494efdd989b1585 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : v8.runtimestats.browsing_mobile_classic Metric : API:count_avg/browse_media Revision Exit Code N chromium@460670 0 +- N/A 10 good chromium@460681 1 +- N/A 10 bad chromium@460691 1 +- N/A 10 bad chromium@460711 1 +- N/A 10 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 v8.runtimestats.browsing_mobile_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983573811411033792 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4643422616420352 | 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! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Mar 30 2017