Google Calendar test account login auth fails with Chrome binary trying to re-record Top Pages page set. |
||
Issue descriptionFails with browser but works with content shell. Suspect we will have to have someone who wrote/maintains our telemetry test login logic talk with someone on the ISE team, unless there is an immediate idea. Presumptive statement as the record is still running, will confirm on Tuesday when I am back -- without fixing this we can't record an updated Google Calendar story because record_wpr for whatever reason doesn't write the actual new web page replay content when the shell is used. See also http://crbug.com/761563. To repro: 0. Apply this patch (unless it's already merged): https://chromium-review.googlesource.com/c/chromium/src/+/648252 1. Build a release content shell and kick off re-record of the page set: % ninja -C out/Release content_shell % tools/perf/record_wpr --browser=content-shell-release --story top25_page_set rasterize_and_record_micro_top25 2. Wait until Calendar story runs (the third). Note that it runs successfully and shows a rendered calendar page. 3. Now build a release Chrome binary, or use the system browser binary, and re-record again with that binary: % ninja -C out/Release chrome % tools/perf/record_wpr --browser=release --story top25_page_set rasterize_and_record_micro_top25 4. Wait until Calendar story runs. Note that it shows an error page with RPC auth info details. You may also need to hack a couple of files to disable DCHECKs, more info in the CL description of https://chromium-review.googlesource.com/c/chromium/src/+/648349 Passing to Ned for input and routing.
,
Sep 2 2017
Confirmed that wpr file data is successfully written with a Chrome binary, but we can't log in to Calendar with such a binary for some reason, thus we can't record new wpr file for it.
,
Sep 7 2017
Obsolete presuming we complete shift to static pages per issue 762230 . |
||
►
Sign in to add a comment |
||
Comment 1 by wkorman@chromium.org
, Sep 2 2017