system_health.common_desktop failing on Mac builders |
||||
Issue descriptionsystem_health.memory_desktop failing on 2 builders Builders failed on: - Mac 10.11 Perf: https://build.chromium.org/p/chromium.perf/builders/Mac%2010.11%20Perf - Mac Retina Perf: https://build.chromium.org/p/chromium.perf/builders/Mac%20Retina%20Perf https://chromium-swarm.appspot.com/task?id=37bf9c86b1a30110&refresh=10&show_raw=1 is a sample task. The screenshot for the failed page (https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/profiler-file-id_113-2017-08-03_02-08-5623532.png) shows a non google webpage. Not sure how that's happening. I'm going to disable the story.
,
Sep 7 2017
Mac 10.11 does not seem to be consistently failing anymore. The following three, however, still are.
config build history
0 mac-air-10.11 common 1244 FTFT-TFFIIFIFFFFFFFT
1 mac-retina common 1100 ----TTF-FFFFFFTFTFF-
2 mac-pro-10.11 common 1430 --F-F---IIIIIIII--F-
Looking into these
,
Sep 7 2017
Actually it's common, not memory, the ones failing now.
,
Sep 7 2017
Forked off the first two to issue 735434 . Looking now into the pro-10.11.
,
Sep 7 2017
Ok, from: 2 mac-pro-10.11 common 1430 --F-F---IIIIIIII--F- The two recent [F]ailures were single story BATTOR flakes: Exception: TraceImportError: No clock sync markers exist pairing clock domain "BATTOR" with target clock domain "MAC_MACH_ABSOLUTE_TIME". The streak of [I]nfra errors were due to not enough swarming capacity; which seems to have recovered now. I don't think there is anything else to fix here. |
||||
►
Sign in to add a comment |
||||
Comment 1 by zh...@chromium.org
, Aug 23 2017Labels: OS-Mac