Issue metadata
Sign in to add a comment
|
page_cycler_v2.intl_ko_th_vi flakily failing on Nexus 7v2, 6, 5, 9 |
||||||||||||||||||
Issue descriptionRevision range first seen: As far back as the logs go Link to failing step log: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus7v2%20Perf%20%282%29/builds/3432/steps/page_cycler_v2.intl_ko_th_vi/logs/stdio https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus6%20Perf%20%282%29/builds/4386/steps/page_cycler_v2.intl_ko_th_vi/logs/stdio https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf%20%282%29/builds/4484/steps/page_cycler_v2.intl_ko_th_vi/logs/stdio If the test is disabled, please downgrade to Pri-2. It is failing in several different ways, but I think they are all chrome crashes.
,
Dec 20 2016
Mike, can you help us get a callstack from some of the recent failures: https://luci-milo.appspot.com/buildbot/chromium.perf/Android%20Nexus7v2%20Perf%20%282%29/3559 https://luci-milo.appspot.com/buildbot/chromium.perf/Android%20Nexus5%20Perf%20%282%29/4640 https://luci-milo.appspot.com/buildbot/chromium.perf/Android%20Nexus6%20Perf%20%282%29/4651 Then ping me so I can try and cc folks who might be able to help us dig into it.
,
Dec 20 2016
Im seeing this crash...
Is this one of the crashes typically caused by Chrome crashing? Or is it a problem itself.
Traceback (most recent call last):
_RunStoryAndProcessErrorIfNeeded at /b/rr/tmpVF0cS1/w/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py:111
test.DidRunStory(state.platform)
DidRunStory at /b/rr/tmpVF0cS1/w/src/third_party/catapult/telemetry/telemetry/web_perf/timeline_based_measurement.py:312
platform.tracing_controller.StopTracing()
StopTracing at /b/rr/tmpVF0cS1/w/src/third_party/catapult/telemetry/telemetry/core/tracing_controller.py:47
return self._tracing_controller_backend.StopTracing()
StopTracing at /b/rr/tmpVF0cS1/w/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:105
self._IssueClockSyncMarker()
_IssueClockSyncMarker at /b/rr/tmpVF0cS1/w/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:200
self._RecordIssuerClockSyncMarker)
RecordClockSyncMarker at /b/rr/tmpVF0cS1/w/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/chrome_tracing_agent.py:177
raise ChromeClockSyncError('Cannot issue clock sync. No devtools clients')
ChromeClockSyncError: Cannot issue clock sync. No devtools clients
Locals:
devtools_clients : []
record_controller_clock_sync_marker_callback : <bound method TracingControllerBackend._RecordIssuerClockSyncMarker of <telemetry.internal.platform.tracing_controller_backend.TracingControllerBackend object at 0x7fc98f623390>>
sync_id
,
Dec 28 2016
Yep, this is definitely an indicator of Chrome crashing.
,
Jan 11 2017
Looking again at this failure on the Nexus 6 bot. During the failed test, this get output to logcat. If it was just Chrome crashing, Im not sure I would expect the forwarder to also die like this. Not sure. +jbudorick, are these logs expected if Chrome crashes? 2K86J: 01-10 22:47:52.396 3974 22250 E chromium: [0110/224752:ERROR:socket.cc(357)] send: Broken pipe 2K86J: 01-10 22:47:52.396 3974 22250 E chromium: [0110/224752:ERROR:socket.cc(334)] read: Bad file number 2K86J: 01-10 22:47:52.396 3974 22250 E chromium: [0110/224752:ERROR:command.cc(65)] Read() error, endpoint was unexpectedly closed. 2K86J: 01-10 22:47:52.396 3974 22250 E chromium: [0110/224752:ERROR:socket.cc(357)] send: Bad file number 2K86J: 01-10 22:47:52.396 3974 22250 E chromium: [0110/224752:ERROR:device_listener.cc(102)] Host could not connect to server. 2K86J: 01-10 22:47:52.396 3974 22250 E chromium: [0110/224752:ERROR:device_listener.cc(105)] Adb Control connection lost. Listener port: 47984
,
Jan 11 2017
These same logs show up in the Nexus 9 bot for this failure as well... 02657: 01-09 00:28:56.992 26190 22269 E chromium: [0109/002856:ERROR:socket.cc(357)] send: Broken pipe 02657: 01-09 00:28:56.992 26190 22269 E chromium: [0109/002856:ERROR:socket.cc(334)] read: Bad file number 02657: 01-09 00:28:56.992 26190 22269 E chromium: [0109/002856:ERROR:command.cc(65)] Read() error, endpoint was unexpectedly closed. 02657: 01-09 00:28:56.992 26190 22269 E chromium: [0109/002856:ERROR:socket.cc(357)] send: Bad file number 02657: 01-09 00:28:56.992 26190 22269 E chromium: [0109/002856:ERROR:device_listener.cc(102)] Host could not connect to server. 02657: 01-09 00:28:56.992 26190 22269 E chromium: [0109/002856:ERROR:device_listener.cc(105)] Adb Control connection lost. Listener port: 42581
,
Jan 11 2017
This is one of the tests that is part of www. crbug.com/667470 .
,
Jan 12 2017
Un-CCing myself. Feel free to re-CC me if necessary.
,
Jan 12 2017
#5: I don't think the device_listener ones are expected on chrome crash. Not sure about the others.
,
Aug 1
|
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by rnep...@chromium.org
, Dec 6 2016