webrtc.* telemetry tests don't work with --browser=system |
|||||
Issue descriptionChrome Version: 58.0.3029.110 (Official Build) (64-bit) OS: Linux What steps will reproduce the problem? (1) Sync past https://chromium.googlesource.com/chromium/src/+/25e51e9509c43a2475ee820cf83a37df3e9ececb (2) Run $ tools/perf/run_benchmark webrtc.getusermedia --browser=system What is the expected result? webrtc.* tests should execute. What happens instead? The browser opened by telemetry crashes. This is because the field trials introduced on https://chromium.googlesource.com/chromium/src/+/25e51e9509c43a2475ee820cf83a37df3e9ececb If we revert it, the telemetry tests execute normally. Also, the telemetry tests work if we run with --browser-executable=out/Release/chrome so that's why it hasn't failed on the bots. FYI: If you are reading this after https://chromium-review.googlesource.com/c/506017/ lands, run instead $ tools/perf/run_benchmark webrtc --browser=system
,
May 16 2017
,
May 16 2017
> This is because the field trials introduced on https://chromium.googlesource.com/chromium/src/+/25e51e9509c43a2475ee820cf83a37df3e9ececb If we revert it, the telemetry tests execute normally. We don't expect Telemetry reference benchmark to always be passing. This will be fixed one we overhaul the ref build. Also the two labels are: Speed>Telemetry --> for Telemetry benchmarks Tests>Telemetry --> for Telemetry integration testing (like gpu tests)
,
Jan 16
,
Jan 16
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ehmaldonado@chromium.org
, May 16 2017