loading.mobile/Wikipedia_3g in performance_webview_test_suite failing on chromium.perf/Android Nexus6 WebView Perf |
|||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of charliea@chromium.org loading.mobile/Wikipedia_3g other(s) in performance_webview_test_suite failing on chromium.perf/Android Nexus6 WebView Perf Builders failed on: - Android Nexus6 WebView Perf: https://ci.chromium.org/p/chrome/builders/luci.chrome.ci/Android%20Nexus6%20WebView%20Perf Link to flakiness dashboard: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=loading.mobile%2FWikipedia_3g&testType=performance_webview_test_suite Log: Traceback (most recent call last): File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 145, in _RunStoryAndProcessErrorIfNeeded state.RunStory(results) File "/b/swarming/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/swarming/w/ir/third_party/catapult/telemetry/telemetry/page/shared_page_state.py", line 304, in RunStory self._current_page.Run(self) File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/page/__init__.py", line 99, in Run self.RunPageInteractions(action_runner) File "/b/swarming/w/ir/tools/perf/page_sets/page_cycler_story.py", line 41, in RunPageInteractions _WEB_CONTENTS_TIMEOUT) File "/b/swarming/w/ir/third_party/catapult/common/py_utils/py_utils/__init__.py", line 150, in WaitFor (timeout, GetConditionString())) TimeoutException: Timed out while waiting 180s for HasReachedQuiescence.
,
Dec 11
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/16dd990a140000
,
Dec 12
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/471e5cf61e4cf3b375cdf4e566fd9b72fd248d65 commit 471e5cf61e4cf3b375cdf4e566fd9b72fd248d65 Author: Charlie Andrews <charliea@chromium.org> Date: Wed Dec 12 01:44:53 2018 Disable wikipedia_3g on N6 Webview TBR=crouleau@chromium.org CC=kouhei@chromium.org,ksakamoto@chromium.org Bug: 914100 Change-Id: Ie5bb8c15ea8b8bf8dcc49cd53bd917df7784f30b Reviewed-on: https://chromium-review.googlesource.com/c/1372727 Reviewed-by: Charlie Andrews <charliea@chromium.org> Commit-Queue: Charlie Andrews <charliea@chromium.org> Cr-Commit-Position: refs/heads/master@{#615766} [modify] https://crrev.com/471e5cf61e4cf3b375cdf4e566fd9b72fd248d65/tools/perf/expectations.config
,
Dec 12
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14847fde140000
,
Dec 12
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/14847fde140000
,
Dec 12
Ned, do you have any idea how to handle a case like this? It looks like in the given revision range, the story started failing because it wasn't reaching quiescence. However, I can't seem to reproduce that failure in bisect.
,
Dec 12
,
Dec 12
Woops - didn't mean to remove ksakamoto@ too.
,
Dec 12
I think for cases like this, we should update the waiting condition to s.t like: wait for element X !== null, the HasReachedQuiescence can be unreliable |
|||
►
Sign in to add a comment |
|||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Dec 11