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

Issue 894235 link

Starred by 3 users
Status: Untriaged
Owner: ----
Cc:
█ uwyiming@chromium.org
nedngu...@google.com
crouleau@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 878390



Sign in to add a comment

WPR: file listed in archive results in read operation timed out

Project Member Reported by sullivan@chromium.org, Oct 10 
I'm trying to re-record the load:tools:weather story for system health desktop. The filenames I have problems with change, but I always get an error like the following:

1) I run this command:
./tools/perf/record_wpr --browser=canary --story-filter=^load:tools:weather:2018$ desktop_system_health_story_set

2) Network errors like this show up in the logs:
(WARNING) 2018-10-10 17:42:36,455 inspector_log._OnMessage:26  DevTools console [network]: Failed to load resource: the server responded with a status of 500 () https://s.w-x.co/weather/assets/42.messages.a09a3de0ae269ee1118b.js

3) I check the WPR logs and see lines like this:

2018/10/10 17:42:33 ServeHTTP(https://s.w-x.co/weather/assets/42.messages.a09a3de0ae269ee1118b.js): RoundTrip failed: read tcp 10.1.10.150:51173->151.101.185.63:443: read: operation timed out
2018/10/10 17:42:33 ServeHTTP(https://s.w-x.co/weather/assets/42.messages.a09a3de0ae269ee1118b.js): serving 500, 0 bytes

4) I list the WPR archive and see this line:
GET s.w-x.co /weather/assets/42.messages.a09a3de0ae269ee1118b.js

It seems like the file is in the archive, but something is going wrong with serving it. Archive attached.
system_health_desktop_5d065c47c2.wprgo
1.8 MB Download

Comment 1 by sullivan@chromium.org, Oct 10

Blocking: 878390

Comment 2 by skobes@chromium.org, Oct 11 

I'm seeing similar issues with the re-recording of load:tools:dropbox.  The record step has no network errors but the replay has 11 (plus some JS errors about CORS policy).

(WARNING) 2018-10-11 11:30:16,495 inspector_log._OnMessage:26  DevTools console [network]: Failed to load resource: the server responded with a status of 500 () https://www.dropbox.com/prompt/main_campaign
(WARNING) 2018-10-11 11:30:16,496 inspector_log._OnMessage:26  DevTools console [network]: Failed to load resource: the server responded with a status of 500 () https://bolt.dropbox.com/2/notify/subscribe
(WARNING) 2018-10-11 11:30:16,496 inspector_log._OnMessage:26  DevTools console [network]: Failed to load resource: the server responded with a status of 500 () https://bolt.dropbox.com/2/notify/subscribe
...

The wprgo (attached) seems to contain these URLs:

$ go run third_party/catapult/web_page_replay_go/src/httparchive.go ls tools/perf/page_sets/data/system_health_desktop_5e40e8bb3b.wprgo | grep /prompt/main_campaign
POST www.dropbox.com /prompt/main_campaign
POST www.dropbox.com /prompt/main_campaign

$ go run third_party/catapult/web_page_replay_go/src/httparchive.go ls tools/perf/page_sets/data/system_health_desktop_5e40e8bb3b.wprgo | grep /2/notify/subscribe
OPTIONS bolt.dropbox.com /2/notify/subscribe
POST bolt.dropbox.com /2/notify/subscribe
system_health_desktop_5e40e8bb3b.wprgo
3.2 MB Download

Comment 3 by nedngu...@google.com, Oct 11

Cc: crouleau@chromium.org

Comment 4 by nedngu...@google.com, Oct 13

Cc: uwyiming@chromium.org
Yiming in case he also encountered this :-)

Comment 5 by sullivan@chromium.org, Oct 15

Labels: -Pri-3 Pri-2
Upping priority since this could potentially be causing benchmark stability issues.

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

Components: Test>Telemetry

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

Components: -Speed>Telemetry
►

Sign in to add a comment