Issue metadata
Sign in to add a comment
|
v8.infinite_scroll-classic_tbmv2 and v8.infinite_scroll_tbmv2 on (102b) GPU on Linux failing on chromium.perf/Linux Perf |
||||||||||||||||||||
Issue descriptionRevision range first seen: https://test-results.appspot.com/revision_range?start=458334&end=458409 Link to failing step log: https://build.chromium.org/p/chromium.perf/builders/Linux%20Perf/builds/496/steps/v8.infinite_scroll-classic_tbmv2%20on%20%28102b%29%20GPU%20on%20Linux Builders failed on: - Linux Perf: https://build.chromium.org/p/chromium.perf/builders/Linux%20Perf If the test is disabled, please downgrade to Pri-2.
,
Mar 28 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983857273777393248
,
Mar 28 2017
I'm not sure the android and linux issues are the same. On android it just looks flaky. On linux, it is failing every time. The failure also seems to manifest slightly differently. On android it is a crash. On linux memory dumps are timing out:
TracingTimeoutException: Exception raised while sending a Tracing.requestMemoryDump request:
Traceback (most recent call last):
File "/b/s/w/ir9CxHqK/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/tracing_backend.py", line 204, in DumpMemory
response = self._inspector_websocket.SyncRequest(request, timeout)
File "/b/s/w/ir9CxHqK/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_websocket.py", line 110, in SyncRequest
res = self._Receive(timeout)
File "/b/s/w/ir9CxHqK/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_websocket.py", line 149, in _Receive
data = self._socket.recv()
File "/b/s/w/ir9CxHqK/third_party/catapult/telemetry/third_party/websocket-client/websocket/_core.py", line 293, in recv
opcode, data = self.recv_data()
File "/b/s/w/ir9CxHqK/third_party/catapult/telemetry/third_party/websocket-client/websocket/_core.py", line 310, in recv_data
opcode, frame = self.recv_data_frame(control_frame)
File "/b/s/w/ir9CxHqK/third_party/catapult/telemetry/third_party/websocket-client/websocket/_core.py", line 323, in recv_data_frame
frame = self.recv_frame()
File "/b/s/w/ir9CxHqK/third_party/catapult/telemetry/third_party/websocket-client/websocket/_core.py", line 357, in recv_frame
return self.frame_buffer.recv_frame()
File "/b/s/w/ir9CxHqK/third_party/catapult/telemetry/third_party/websocket-client/websocket/_abnf.py", line 336, in recv_frame
self.recv_header()
File "/b/s/w/ir9CxHqK/third_party/catapult/telemetry/third_party/websocket-client/websocket/_abnf.py", line 286, in recv_header
header = self.recv_strict(2)
File "/b/s/w/ir9CxHqK/third_party/catapult/telemetry/third_party/websocket-client/websocket/_abnf.py", line 371, in recv_strict
bytes_ = self.recv(min(16384, shortage))
File "/b/s/w/ir9CxHqK/third_party/catapult/telemetry/third_party/websocket-client/websocket/_core.py", line 427, in _recv
return recv(self.sock, bufsize)
File "/b/s/w/ir9CxHqK/third_party/catapult/telemetry/third_party/websocket-client/websocket/_socket.py", line 83, in recv
raise WebSocketTimeoutException(message)
WebSocketTimeoutException: timed out
Locals:
request : {'method': 'Tracing.requestMemoryDump', 'id': 0}
timeout : 90
,
Mar 28 2017
,
Mar 28 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: linux_perf_bisect Benchmark : v8.infinite_scroll-classic_tbmv2 Metric : memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_std/facebook Revision Exit Code N chromium@458332 0 +- N/A 2 good chromium@458413 0 +- N/A 2 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=facebook v8.infinite_scroll-classic_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983857273777393248 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5801154404941824 | 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 28 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983852328940596768
,
Mar 28 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: linux_perf_bisect Benchmark : v8.infinite_scroll-classic_tbmv2 Metric : memory:chrome:all_processes:reported_by_chrome:v8:heap:large_object_space:effective_size_sum/facebook Revision Exit Code N chromium@458327 0 +- N/A 4 good chromium@458502 0 +- N/A 4 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=facebook v8.infinite_scroll-classic_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983852328940596768 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5224037938102272 | 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 28 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983843438056078720
,
Mar 28 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: linux_perf_bisect Benchmark : v8.infinite_scroll_tbmv2 Metric : memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_avg/facebook Revision Exit Code N chromium@458301 0 +- N/A 2 good chromium@458536 0 +- N/A 2 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=facebook v8.infinite_scroll_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983843438056078720 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5808363138449408 | 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 28 2017
This is also failing on nexus 5x webview bot, I'll start a bisect there.
,
Mar 28 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983839867497581952
,
Mar 28 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : v8.infinite_scroll_tbmv2 Metric : BenchmarkDuration/BenchmarkDuration Revision Exit Code N chromium@459780 0 +- N/A 2 good chromium@459820 0 +- N/A 2 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=BenchmarkDuration v8.infinite_scroll_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983839867497581952 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5240782673412096 | 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!
,
Jul 10 2017
Most of these bugs re v8.infinite_scroll_tbmv2 should be handled through Issue 724262 .
,
Jul 11 2017
,
Jul 11 2017
The benchmark is removed. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by altimin@chromium.org
, Mar 24 2017