loading.mobile/OLX_3g in performance_webview_test_suite failing on chromium.perf/Android Nexus5X WebView Perf |
|||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of charliea@chromium.org loading.mobile/OLX_3g in performance_webview_test_suite failing on chromium.perf/Android Nexus5X WebView Perf Builders failed on: - Android Nexus5X WebView Perf: https://ci.chromium.org/p/chrome/builders/luci.chrome.ci/Android%20Nexus5X%20WebView%20Perf It looks like this test got flaky somewhere between 615267 (good) and 616260 (bad). It was still failing before that, but the rate seemed to be much lower. Going to disable and kick off a bisect for now.
,
Jan 4
,
Jan 4
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/149cf746940000
,
Jan 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/db624110317d01efa78cd32e7be1524190e1beb0 commit db624110317d01efa78cd32e7be1524190e1beb0 Author: Charlie Andrews <charliea@chromium.org> Date: Fri Jan 04 21:09:35 2019 Disable loading.mobile/OLX_3g on Nexus5X_Webview NOTRY=true TBR=crouleau@chromium.org, kouhei@chromium.org, ksakamoto@chromium.org Bug: 919191 Change-Id: I5c805aa62eb687db3f6993a3444aaf4cd438a190 Reviewed-on: https://chromium-review.googlesource.com/c/1396606 Reviewed-by: Charlie Andrews <charliea@chromium.org> Commit-Queue: Charlie Andrews <charliea@chromium.org> Cr-Commit-Position: refs/heads/master@{#620064} [modify] https://crrev.com/db624110317d01efa78cd32e7be1524190e1beb0/tools/perf/expectations.config
,
Jan 4
😿 Pinpoint job stopped with an error. https://pinpoint-dot-chromeperf.appspot.com/job/149cf746940000 All of the runs failed. The most common error (20/20 runs) was: TimeoutException: Timed out while waiting 180s for HasReachedQuiescence.
,
Jan 7
Hmmm, looks like the bisect is having even more problems with the story than the waterfall is. Going to kick this over to the benchmark owners for investigation. My guess is that we should be waiting for a specific element to appear onscreen instead of waiting for quiescence, which looks flaky. |
|||
►
Sign in to add a comment |
|||
Comment 1 by charliea@chromium.org
, Jan 4