New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 753704 link

Starred by 4 users
Status: Archived
Owner: ----
Closed: Nov 12
Cc:
█ matthew....@intel.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Fail to run Telemetry WebRTC benchmark

Reported by shaofeng...@intel.com, Aug 9 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36
Platform: 9719.0.0 dev-channel test

Steps to reproduce the problem:
1. Fetch the source code of chromium
2. Execute Telemetry WebRTC benchmark from host via 
<Chromium_Home>/src/tools/perf/run_benchmark --remote <Chromebook IP> --browser=cros_chrome webrtc

What is the expected behavior?
The benchmark work well, and the result for "720p_call_45s" is available in results html

What went wrong?
Below error message is shown
[  PASSED  ] 4 tests.
[  FAILED  ] 5 tests, listed below:
[  FAILED  ]  multiple_peerconnections
[  FAILED  ]  30s_datachannel_transfer
[  FAILED  ]  hd_local_stream_10s
[  FAILED  ]  720p_call_45s
[  FAILED  ]  canvas_capture_peer_connection

5 FAILED TESTS

Did this work before? N/A 

Chrome version: 61.0.3150.0  Channel: dev
OS Version: R61-9719.0.0
Flash Version: 26.0.0.137

The telemetry version we used is below

commit d1c6f933beebe20d6afce1cc25122164d28aeb1c
Author: Yuki Shiino <yukishiino@chromium.org>
Date:   Wed Jul 26 09:11:41 2017 +0000

Comment 1 by chunbo....@intel.com, Aug 11 2017 

The same failure also happened on ChromeOS R62-9802.0.0(Channel: dev), together with telemetry version as following: 
commit 3b27f0326c66d07ca72c5c197bbb28e4d7dc68fb
Author: Alexander Alekseev <alemate@chromium.org>
Date:   Thu Aug 3 06:59:56 2017 +0000

Comment 2 by zalcorn@chromium.org, Aug 11 2017

Components: Tests>Telemetry

Comment 3 by matthew....@intel.com, Aug 24 2017 

Can you please direct cc me? I have a list of TAMs and Google engrs to add.

Comment 4 by sullivan@chromium.org, Aug 25 2017

Cc: matthew....@intel.com

Comment 5 by chunbo....@intel.com, Nov 10 2017 

I've tested ChromeOS R64-10105.0.0(Channel: dev), together with telemetry version as following: 
commit	01402a48c7112dee07d962c5c1f79759754fbda2
author	Bret Sepulveda <bsep@chromium.org>	Fri Sep 01 02:39:46 2017

This failure is gone now. Please help verify this bug and the fixing accordingly.
Project Member

Comment 6 by sheriffbot@chromium.org, Nov 12

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment