V8.runtimestats.browsing_desktop failing on mac pro 10.11 perf bot |
||
Issue description
Traceback (most recent call last):
File "/b/s/w/ir/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 98, in _RunStoryAndProcessErrorIfNeeded
state.WillRunStory(story)
File "/b/s/w/ir/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 75, in traced_function
return func(*args, **kwargs)
File "/b/s/w/ir/third_party/catapult/telemetry/telemetry/page/shared_page_state.py", line 241, in WillRunStory
archive_path, page.make_javascript_deterministic)
File "/b/s/w/ir/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 75, in traced_function
return func(*args, **kwargs)
File "/b/s/w/ir/third_party/catapult/telemetry/telemetry/core/network_controller.py", line 42, in StartReplay
make_javascript_deterministic)
File "/b/s/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/network_controller_backend.py", line 193, in StartReplay
local_ports = self._StartReplayServer()
File "/b/s/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/network_controller_backend.py", line 227, in _StartReplayServer
return self._wpr_server.StartServer()
File "/b/s/w/ir/third_party/catapult/telemetry/telemetry/internal/util/webpagereplay_go_server.py", line 283, in StartServer
''.join(self._LogLines()))
ReplayNotStartedError: Web Page Replay failed to start. Log output:
2017/09/16 16:00:49 Loading cert from /b/s/w/ir/third_party/catapult/web_page_replay_go/wpr_cert.pem
2017/09/16 16:00:49 Loading key from /b/s/w/ir/third_party/catapult/web_page_replay_go/wpr_key.pem
2017/09/16 16:00:49 Loading script from /b/s/w/ir/third_party/catapult/web_page_replay_go/deterministic.js
,
Sep 20 2017
We just recently switched from the old version of wpr to the go version. We have a 30 second timeout when starting the wprgo server. It could be possible that the switch to wprgo makes it take longer than 30 seconds to start the server. There also appears to be a pretty clear line in the sand where the benchmark starts failing, so going bisect there to try and confirm this suspicion.
,
Sep 20 2017
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12ff4d40780000
,
Sep 21 2017
📍 Pinpoint job completed. https://pinpoint-dot-chromeperf.appspot.com/job/12ff4d40780000
,
Nov 7
This regression has been open for half a year. It's not very actionable and the regression has been in all Chrome user's hands for months. |
||
►
Sign in to add a comment |
||
Comment 1 by rnep...@chromium.org
, Sep 20 2017