system_health.common_desktop times out after 3 hours |
|||
Issue descriptionsystem_health.common_desktop failing on 2 builders Builders failed on: - Linux Perf: https://build.chromium.org/p/chromium.perf/builders/Linux%20Perf - Mac Retina Perf: https://build.chromium.org/p/chromium.perf/builders/Mac%20Retina%20Perf The benchmark took 3 hours and timed out. We've already bumped the timeout on this test; I don't think we want to bump it more. Is there any way we can make the test run faster?? https://chromium-swarm.appspot.com/task?id=36e6be7f1b61ec10&refresh=10&show_raw=1 is an example run.
,
Jun 22 2017
loading.desktop times out as well, on Linux Perf. https://chromium-swarm.appspot.com/task?id=36e6bdd65163df10&refresh=10&show_raw=1 Probably related.
,
Jun 22 2017
They may or may not related. For simplicity, I think let just handled them separately. For now, I think we should disable facebook page.
,
Jul 18 2017
https://uberchromegw.corp.google.com/i/chromium.perf/builders/Mac%20Air%2010.11%20Perf?numbuilds=200 Mac Air bot is also timing out on system_health.common_desktop test. The below error was logged, but unsure if it was caused just by swarming timing out. I'd like to add timestamps to the telemetry python logging if that sounds alright. https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FMac_Air_10.11_Perf%2F1068%2F%2B%2Frecipes%2Fsteps%2Fsystem_health.common_desktop_on_Intel_GPU_on_Mac_on_Mac-10.11%2F0%2Fstdout ERROR:root:Git hash returned from BattOr was not as expected: [0718/090402.041548:FATAL:battor_agent_bin.cc(91)] Fatal error when communicating with the BattOr: TOO MANY COMMAND RETRIES Traceback (most recent call last): File "/b/s/w/ir/third_party/catapult/common/battor/battor/battor_wrapper.py", line 162, in _FlashBattOr device_git_hash = self.GetFirmwareGitHash() File "/b/s/w/ir/third_party/catapult/common/battor/battor/battor_wrapper.py", line 392, in GetFirmwareGitHash int(self._git_hash, 16)
,
Jul 18 2017
Uploaded https://chromium-review.googlesource.com/c/576611/ to add timestamps the run_benchmark logging
,
Jul 19
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 19
This is no longer the case with the OBBS |
|||
►
Sign in to add a comment |
|||
Comment 1 by martiniss@chromium.org
, Jun 22 2017