Issue metadata
Sign in to add a comment
|
v8.runtime_stats.top_25 failure on Linux chromium.perf at <revisionrange> |
||||||||||||||||||||||||
Issue descriptionRevision range first seen: 447774 - 447860 Link to failing step log: https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FLinux_Perf%2F360%2F%2B%2Frecipes%2Fsteps%2Fv8.runtime_stats.top_25_on__102b__GPU_on_Linux_on_Ubuntu-14.04%2F0%2Fstdout Looks like it's producing all the data, but not properly shutting down the browser: [ OK ] http://www.sina.com.cn (105075 ms) WARNING:root:Failed to gracefully shutdown. WARNING:root:Proceed to kill the browser. INFO:root:Try printing formatted exception: None None None Traceback (most recent call last): RunBenchmark at /b/s/w/irW41_Zb/third_party/catapult/telemetry/telemetry/internal/story_runner.py:380 benchmark.ShouldTearDownStateAfterEachStorySetRun()) Run at /b/s/w/irW41_Zb/third_party/catapult/telemetry/telemetry/internal/story_runner.py:259 _RunStoryAndProcessErrorIfNeeded(story, results, state, test) _RunStoryAndProcessErrorIfNeeded at /b/s/w/irW41_Zb/third_party/catapult/telemetry/telemetry/internal/story_runner.py:116 state.DidRunStory(results) traced_function at /b/s/w/irW41_Zb/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py:52 return func(*args, **kwargs) DidRunStory at /b/s/w/irW41_Zb/third_party/catapult/telemetry/telemetry/page/shared_page_state.py:153 self._current_tab.Close() traced_function at /b/s/w/irW41_Zb/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py:52 return func(*args, **kwargs) Close at /b/s/w/irW41_Zb/third_party/catapult/telemetry/telemetry/internal/browser/tab.py:100 self._tab_list_backend.CloseTab(self.id) CloseTab at /b/s/w/irW41_Zb/third_party/catapult/telemetry/telemetry/internal/backends/chrome/tab_list_backend.py:67 py_utils.WaitFor(lambda: tab_id not in self.IterContextIds(), timeout=5) WaitFor at /b/s/w/irW41_Zb/third_party/catapult/common/py_utils/py_utils/__init__.py:132 (timeout, GetConditionString())) TimeoutException: Timed out while waiting 5s for py_utils.WaitFor(lambda: tab_id not in self.IterContextIds(), timeout=5).
,
Feb 13 2017
I kicked off a bisect. But I may not fully understand which metrics the test is supposed to produce. It looks like the ones I bisected actually stop coming in a little bit before the build fails: https://chromeperf.appspot.com/report?sid=269c01e74de77d4386c15332109d9367ab37442ef0c1e7b51a0bdbe479b1f09d Is there a better metric to bisect?
,
Feb 13 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: linux_perf_bisect Benchmark : v8.runtime_stats.top_25 Metric : Runtime:count_avg/http___www.sina.com.cn Revision Exit Code N chromium@447128 0 +- N/A 20 good chromium@447860 0 +- N/A 20 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=http...www.sina.com.cn v8.runtime_stats.top_25 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8987757328675349792 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5781764632477696 | 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!
,
Feb 13 2017
I'll try another bisect with no story-filter.
,
Feb 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8987753113568310944
,
Feb 14 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: linux_perf_bisect Benchmark : v8.runtime_stats.top_25 Metric : Runtime:duration_avg/Runtime:duration_avg Revision Exit Code N chromium@447128 1 +- N/A 20 good chromium@447860 1 +- N/A 20 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 v8.runtime_stats.top_25 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8987753113568310944 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5831119980724224 | 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!
,
Feb 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8987007359787489728
,
Feb 22 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: linux_perf_bisect Benchmark : v8.runtime_stats.top_25 Metric : API:count_avg/API:count_avg Revision Exit Code N chromium@446900 0 +- N/A 3 good chromium@447860 0 +- N/A 3 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 v8.runtime_stats.top_25 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8987007359787489728 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5893870887370752 | 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 29 2017
,
Jan 16
,
Jan 16
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Feb 13 2017