benchmarks.system_health_smoke_test.SystemHealthBenchmarkSmokeTest.system_health.memory_desktop.browse:tools:maps is flaky |
|||||||
Issue descriptionThis crashes pretty often: https://luci-milo.appspot.com/p/chromium/builders/luci.chromium.ci/Linux%20Tests%20%28dbg%29%281%29/607 https://chromium-swarm.appspot.com/task?id=3b46c856c126be10&refresh=10&show_raw=1&wide_logs=true Retry: https://chromium-swarm.appspot.com/task?id=3b478f00d5056410&refresh=10&show_raw=1&wide_logs=true https://luci-milo.appspot.com/p/chromium/builders/luci.chromium.ci/Linux%20Tests%20%28dbg%29%281%29/596 https://chromium-swarm.appspot.com/task?id=3b45aa857908b310&refresh=10&show_raw=1&wide_logs=true
,
Jan 25 2018
,
Jan 29 2018
Looks like this is only flaky on Linux Dbg config, I am guessing that we just need a longer timeout for whatever action was stuck.
,
Jan 29 2018
This is flaky on Linux Dbg only: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=telemetry_perf_unittests&showExpectations=true&tests=benchmarks%2Fsystem_health_smoke_test%2FSystemHealthBenchmarkSmokeTest%2Fsystem_health%2Fmemory_desktop%2Fbrowse%3Atools%3Amaps
,
Jan 29 2018
To be clear, from all of the failures that I have seen, the swarming job times out because that test crashed, and then the 2nd or 3rd retry times out. So from what I can tell, it's a crashing problem, not strictly a thing being stuck.
,
Jan 29 2018
Hinoka: this is the only failing stack I've seen so far: TimeoutException: Timed out while waiting 60s for IsJavaScriptExpressionTrue. Console output: Can you give the log link that shows the test crashed?
,
Jan 29 2018
Oh I assumed it was a crash because I saw this: (/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py:487 _ConvertExceptionFromInspectorWebsocket) The app is probably crashed: Found Minidump: True Stack Trace: If I misinterpreted that, then ignore my prior statement.
,
Jan 30 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0c0fb93082de24033db27bc03849b744ba0bb9cb commit 0c0fb93082de24033db27bc03849b744ba0bb9cb Author: Ned Nguyen <nednguyen@google.com> Date: Tue Jan 30 12:48:07 2018 Increase timeout when waiting for page to be updated in browse:tools:maps test Bug: 806057 Change-Id: Ida24c4484fa417cc413e512a845103e5bcef7d2d Reviewed-on: https://chromium-review.googlesource.com/891687 Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org> Commit-Queue: Ned Nguyen <nednguyen@google.com> Cr-Commit-Position: refs/heads/master@{#532848} [modify] https://crrev.com/0c0fb93082de24033db27bc03849b744ba0bb9cb/tools/perf/page_sets/system_health/browsing_stories.py
,
Jul 20
I just got this three times in a row on https://chromium-review.googlesource.com/c/chromium/src/+/1141735/2 https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-marshmallow-arm64-rel/42948 https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-marshmallow-arm64-rel/43015 https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-marshmallow-arm64-rel/43125 I don't think I've broken anything.
,
Aug 2
,
Jan 16
(6 days ago)
,
Jan 16
(6 days ago)
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by hinoka@chromium.org
, Jan 25 2018