New issue
Advanced search Search tips

Issue 789698 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Dec 20
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug

Blocked on:
issue 788796


Show other hotlists

Hotlists containing this issue:
Hotlist-1


Sign in to add a comment

reference builds missing for various linux-release video.html?src_*

Project Member Reported by crouleau@chromium.org, Nov 29 2017

Issue description

The run is failing with an abstruse error https://logs.chromium.org/v/?s=chrome%2Fbb%2Fchromium.perf%2FLinux_Perf%2F2031%2F%2B%2Frecipes%2Fsteps%2Fmedia.desktop.reference_on_NVIDIA_GPU_on_Linux%2F0%2Fstdout :

Traceback (most recent call last):
  File "/b/rr/tmpH26DPW/rw/checkout/scripts/slave/recipe_modules/swarming/resources/standard_isolated_script_merge.py", line 45, in <module>
    sys.exit(main())
  File "/b/rr/tmpH26DPW/rw/checkout/scripts/slave/recipe_modules/swarming/resources/standard_isolated_script_merge.py", line 41, in main
    return StandardIsolatedScriptMerge(args.output_json, args.jsons_to_merge)
  File "/b/rr/tmpH26DPW/rw/checkout/scripts/slave/recipe_modules/swarming/resources/standard_isolated_script_merge.py", line 24, in StandardIsolatedScriptMerge
    shard_results_list.append(json.load(f))
  File "/usr/lib/python2.7/json/__init__.py", line 290, in load
    **kw)
  File "/usr/lib/python2.7/json/__init__.py", line 338, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
    raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
Blockedon: 788796
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.
Cc: wolenetz@chromium.org
Summary: reference builds missing for various linux-release video.html?src_* (was: reference builds missing for linux-release video.html?src_tulip2.vp9.webm_Regular-3G)
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


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
Looks like the the media.desktop reference are timing out: https://chromium-swarm.appspot.com/task?id=3a868207d7c12310&refresh=10&show_raw=1
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.

Cc: crouleau@chromium.org
Components: Speed>Telemetry
Owner: ----
Status: Available (was: Assigned)
No idea why this is failing on the bots but passing locally.
Project Member

Comment 9 by sheriffbot@chromium.org, Dec 20

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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
Status: Archived (was: Untriaged)

Comment 11 by benhenry@google.com, Jan 16 (6 days ago)

Components: Test>Telemetry

Comment 12 by benhenry@google.com, Jan 16 (6 days ago)

Components: -Speed>Telemetry

Sign in to add a comment