Issue metadata
Sign in to add a comment
|
smoothness.maps failing on windows 7 Nvidia GPU bot |
||||||||||||||||||||||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%207%20Nvidia%20GPU%20Perf/builds/928 For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Jun 27 2017
=== Auto-CCing suspected CL author hbos@chromium.org === Hi hbos@chromium.org, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Test failure found with culprit Suspected Commit Author : hbos Commit : d6144f20a4e3e525bc3e52d097a6c20c90d615ed Date : Mon Jun 26 15:04:04 2017 Subject: WebRtcMediaStreamAdapterMap added. Bisect Details Configuration: winx64nvidia_perf_bisect Benchmark : smoothness.maps Metric : benchmark_duration/benchmark_duration Revision Exit Code N chromium@482264 1 +- N/A 2 good chromium@482275 1 +- N/A 2 good chromium@482276 0 +- N/A 2 bad <-- chromium@482277 0 +- N/A 2 bad chromium@482278 0 +- N/A 2 bad chromium@482281 0 +- N/A 2 bad chromium@482286 0 +- N/A 2 bad chromium@482307 0 +- N/A 2 bad chromium@482349 0 +- N/A 2 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests smoothness.maps Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8975617261840701392 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5811462498418688 | 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!
,
Jun 27 2017
Sorry for the noise, hbos. Trying to bisect a flaky test failure, the bisect in #2 says your CL makes the test PASS. Will try to kick off another.
,
Jun 27 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8975611947591455152
,
Jun 27 2017
=== Auto-CCing suspected CL author nicholss@chromium.org === Hi nicholss@chromium.org, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Test failure found with culprit Suspected Commit Author : nicholss Commit : 0f9d5e4dc08bc9045b44cc3d0e0b24eff251f0f2 Date : Mon Jun 26 17:35:31 2017 Subject: Wired up the in-session menu but not the implementation of the options. Bisect Details Configuration: winx64nvidia_perf_bisect Benchmark : smoothness.maps Metric : benchmark_duration/benchmark_duration Revision Exit Code N chromium@482264 1 +- N/A 20 good chromium@482286 1 +- N/A 20 good chromium@482297 1 +- N/A 20 good chromium@482302 1 +- N/A 20 good chromium@482305 1 +- N/A 20 good chromium@482306 1 +- N/A 20 good chromium@482307 0 +- N/A 20 bad <-- chromium@482349 0 +- N/A 20 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests smoothness.maps Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8975611947591455152 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6336632443109376 | 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!
,
Jun 27 2017
Sorry for the noise. Looks like this failure is too flaky to bisect.
,
Jun 27 2017
Disabling story for now.
,
Aug 7 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jun 27 2017