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

Issue 807010 link

Starred by 2 users
Status: Untriaged
Owner: ----
Cc:
█ xunji...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Telemetry tests should not be passing https_cert_file and https_key_file to WprGo

Project Member Reported by mahmadi@chromium.org, Jan 29 2018 
Currently webpagereplay_go_server.py passes https_cert_file and https_key_file to WprGo.

WprGo's cert file may need to change from time to time (see https://github.com/catapult-project/catapult/issues/4208). This makes archives recorded with the old certificate unusable.

Comment 1 by mahmadi@chromium.org, Jan 30 2018 

Once the support is added to WprGo to store certificate information in the archives themselves and convert existing archives to the new format, telemetry should update its existing archives and stop passing those arguments to WprGo. Instead it should rely on the public key hash which WprGo prints in the terminal to pass to Chrome.

Comment 2 by nedngu...@google.com, Jan 30 2018

Cc: xunji...@chromium.org

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

Components: Test>Telemetry

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

Components: -Speed>Telemetry
►

Sign in to add a comment