tab_switching.tough_energy_cases.reference timing out on Windows Zenbook Perf |
||||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%20Zenbook%20Perf/builds/118 is an example build. Looks like an infrastructure issue; I don't know if a particular commit introduced this. https://chromium-swarm.appspot.com/task?id=335ad4537c93c710&refresh=10&show_raw=1 is a run which times out. https://chromium-swarm.appspot.com/task?id=335ad458b863e410&refresh=10&show_raw=1 is a run which successfully completes. I noticed that this log line appears when it completes successfully: c:\b\s\w\irsfixqs\tools\perf\measurements\tab_switching.py:71: UserWarning: Function WaitFor is deprecated. It will no longer be supported on June 01, 2017. Please remove it or switch to an alternative before that time. telemetry.core.utils.WaitFor() is being deprecated. Please use catapult.common.py_utils.WaitFor() instead. Could that be related? https://cs.chromium.org/chromium/src/tools/perf/measurements/tab_switching.py?q=tab_switching.py&sq=package:chromium&l=71 is the line in question.
,
Dec 28 2016
Hmm, don't think it was caused by the deprecated thing. Although maybe... Also, noticed something. The logs for the timed out test look like this: INFO:root:Issuing command to ts_proxy_server: set rtt 0 INFO:root:Issuing command to ts_proxy_server: set inkbps 0 Comparing these with a successful run, it's missing the following line: INFO:root:Issuing command to ts_proxy_server: set outkbps 0 So maybe the ts_proxy_server is hanging? Not sure what that is exactly...
,
Dec 29 2016
This caused a bunch of jobs to expire today, I believe. The bot was build121-b1; https://chromium-swarm.appspot.com/bot?id=build121-b1&sort_stats=total%3Adesc Relevant build: https://build.chromium.org/p/chromium.perf/builders/Win%2010%20High-DPI%20Perf/builds/133
,
Jan 3 2017
Stephen, can you disable the ref build for this test on Windows?
,
Jan 4 2017
I'll disable the builds on windows :( This also seems to be affecting the Win High-DPI bot. https://luci-milo.appspot.com/buildbot/chromium.perf/Win%2010%20High-DPI%20Perf/152 is an example build. Looks like it reliably fails there though.
,
Jan 4 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7fd1d6ba7c33d34af70dab4f7b9646b51c039500 commit 7fd1d6ba7c33d34af70dab4f7b9646b51c039500 Author: martiniss <martiniss@chromium.org> Date: Wed Jan 04 21:09:10 2017 Disable tab_switching.tough_energy_cases on win BUG=677311 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq Review-Url: https://codereview.chromium.org/2612673002 Cr-Commit-Position: refs/heads/master@{#441463} [modify] https://crrev.com/7fd1d6ba7c33d34af70dab4f7b9646b51c039500/tools/perf/benchmarks/tab_switching.py
,
Feb 14 2017
Ned - is this a benchmark we cna turndown?
,
Feb 14 2017
This benchmark is unowned, poorly architected & disabled on almost every platform. Let turn this down. + bccheng: FYI |
||||
►
Sign in to add a comment |
||||
Comment 1 by martiniss@chromium.org
, Dec 28 2016Components: Infra>Client>Perf
Labels: -Pri-3 Pri-2