telemetry_perf_unittests failing on c on Mac-10.11 |
|||||||||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of gab@chromium.org telemetry_perf_unittests failing on c on Mac-10.11 Builders failed on: - https://uberchromegw.corp.google.com/i/chromium.mac/builders/Mac10.11%20Tests Latest Error: Traceback (most recent call last): _RunStoryAndProcessErrorIfNeeded at /b/s/w/ir/third_party/catapult/telemetry/telemetry/internal/story_runner.py:147 test.DidRunStory(state.platform, results) DidRunStory at /b/s/w/ir/third_party/catapult/telemetry/telemetry/web_perf/timeline_based_measurement.py:290 trace_result, _ = platform.tracing_controller.StopTracing() StopTracing at /b/s/w/ir/third_party/catapult/telemetry/telemetry/core/tracing_controller.py:53 return self._tracing_controller_backend.StopTracing() StopTracing at /b/s/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:130 self._IssueClockSyncMarker() _IssueClockSyncMarker at /b/s/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:234 self._RecordIssuerClockSyncMarker) RecordClockSyncMarker at /b/s/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/chrome_tracing_agent.py:178 raise ChromeClockSyncError('Cannot issue clock sync. No devtools clients') ChromeClockSyncError: Cannot issue clock sync. No devtools clients @https://logs.chromium.org/v/?s=chromium%2Fbb%2Fchromium.mac%2FMac10.11_Tests%2F23413%2F%2B%2Frecipes%2Fsteps%2Ftelemetry_perf_unittests_on_Mac-10.11%2F0%2Fstdout
,
Feb 15 2018
,
Feb 15 2018
,
Feb 15 2018
(sorry wrong sherriff-o-matic link... this is about telemetry_perf_unittests failing on c on Mac-10.11)
,
Feb 15 2018
Based on the log, it looks like I need to bump up the wpr archive loading time: 2018/02/15 04:16:53 Loading cert from /b/s/w/ir/third_party/catapult/web_page_replay_go/wpr_cert.pem 2018/02/15 04:16:53 Loading key from /b/s/w/ir/third_party/catapult/web_page_replay_go/wpr_key.pem 2018/02/15 04:16:53 Loading script from /b/s/w/ir/third_party/catapult/web_page_replay_go/deterministic.js 2018/02/15 04:16:53 Loading archive file from /b/s/w/ir/tools/perf/page_sets/data/system_health_desktop_055.wprgo 2018/02/15 04:18:03 Opened archive /b/s/w/ir/tools/perf/page_sets/data/system_health_desktop_055.wprgo 2018/02/15 04:18:03 Use Ctrl-C to exit. 2018/02/15 04:18:03 Starting server on https://127.0.0.1:49299 2018/02/15 04:18:03 Starting server on http://127.0.0.1:49300 (The current timeout is 60s)
,
Feb 15 2018
,
Feb 15 2018
The following revision refers to this bug: https://chromium.googlesource.com/catapult/+/52a9fc2dbddbcb7286aba363e8fe9e44879bd5f2 commit 52a9fc2dbddbcb7286aba363e8fe9e44879bd5f2 Author: nednguyen <nednguyen@google.com> Date: Thu Feb 15 17:24:42 2018 Bump up wpr startup timeout to 120s Bug: chromium:812639 Change-Id: I7788a3776a25046d8f5bbc1d60ce7a5a292cf3ea Reviewed-on: https://chromium-review.googlesource.com/921928 Commit-Queue: Ned Nguyen <nednguyen@google.com> Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org> [modify] https://crrev.com/52a9fc2dbddbcb7286aba363e8fe9e44879bd5f2/telemetry/telemetry/internal/util/webpagereplay_go_server.py
,
Feb 16 2018
Some tests in benchmarks.system_health_smoke_test.SystemHealthBenchmarkSmokeTest.system_health.memory_desktop.load are still failing recently. https://uberchromegw.corp.google.com/i/chromium.mac/builders/Mac10.11%20Tests/builds/23422 https://uberchromegw.corp.google.com/i/chromium.mac/builders/Mac10.11%20Tests/builds/23425
,
Feb 16 2018
that is because catapult roll is failing: https://catapult-roll.skia.org/
,
Feb 16 2018
Revert https://chromium-review.googlesource.com/c/catapult/+/923421 hopefully would unblock the roll
,
Feb 16 2018
,
Feb 21 2018
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by gab@chromium.org
, Feb 15 2018Status: Assigned (was: Available)