reference builds missing for various linux-release video.html?src_* |
|||||||||
Issue description
,
Nov 29 2017
Looks like this was revised by a recent change for issue 788796 . I'll wait for that to be resolved and that see if it is still failing.
,
Nov 29 2017
,
Nov 29 2017
Another couple occurrences: linux-release video.htmlo?src_crowd1080_vp9.webm_seek : https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_-napAoM linux-release video.html?src_tulip2.vp9.webm_seek : https://chromeperf.appspot.com/group_report?sid=cfe450e2d7b84904faeed7fed83121c6841656e5a69151317937831d1a279dfe
,
Nov 30 2017
Here's a similar no-ref-trace graph from a different bot (win-high-dpi): https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_8-EoQsM
,
Dec 19 2017
Looks like the the media.desktop reference are timing out: https://chromium-swarm.appspot.com/task?id=3a868207d7c12310&refresh=10&show_raw=1
,
Dec 19 2017
I ran locally using swarming: $ python tools/swarming_client/swarming.py reproduce -S chromium-swarm.appspot.com 3a868207d7c12310 That failed for no good reason: "run_telemetry_benchmark_as_googletest.py: error: argument --isolated-script-test-output: can't open 'out/output.json': [Errno 2] No such file or directory: 'out/output.json'" but it left behind a work/ directory, so I ran $ /usr/bin/python testing/scripts/run_telemetry_benchmark_as_googletest.py tools/perf/run_benchmark media.desktop -v --upload-results --browser=reference --output-format=chartjson --max-failures=5 --output-trace-tag=_ref --isolated-script-test-output=out/output.json --isolated-script-test-perf-output=out/perftest-output.json and that worked just fine. Now I'm retrying the test on a swarming bot: https://chromium-swarm.appspot.com/task?id=3a89b56e68fa1510&refresh=10&show_raw=1 Looks like it's going to time out as well.
,
Dec 19 2017
No idea why this is failing on the bots but passing locally.
,
Dec 20
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
,
Dec 20
,
Jan 16
(6 days ago)
,
Jan 16
(6 days ago)
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by crouleau@chromium.org
, Nov 29 2017