Issue metadata
Sign in to add a comment
|
Most system health stories failing on linux perf bots |
||||||||||||||||||||||
Issue descriptionMost of the stories seem to be failing both on the "common" and "memory" versions of the system_health benchmark. The browser stdout shows: (INFO) 2017-06-07 05:03:49,923 browser.DumpStateUponFailure:374 [6761:6761:0607/050249.507243:ERROR:sandbox_linux.cc(344)] InitializeSandbox() called with multiple threads in process gpu-process. Could this be the cause of the failures? Build with first failures: https://luci-milo.appspot.com/buildbot/chromium.perf/Linux%20Perf/759 With CL range: http://test-results.appspot.com/revision_range?start=477411&end=477510 Will try a return code biect.
,
Jun 21 2017
I think this is probably related to issue 732463
,
Jun 21 2017
,
Jun 21 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: linux_perf_bisect Benchmark : system_health.common_desktop Metric : cpuTimeToFirstMeaningfulPaint_avg/load_social/load_social_pinterest Revision Exit Code N chromium@477410 0 +- N/A 5 good chromium@477510 0 +- N/A 5 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.social.pinterest system_health.common_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976172826480819328 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5548654590427136 | 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
, Jun 21 2017