Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(240)

Issue 1912443002: Reimplement basic PopularUrls page cycler in telemetry. (Closed)

Created:
4 years, 8 months ago by mikecase (-- gone --)
Modified:
4 years, 5 months ago
CC:
chromium-reviews, telemetry-reviews_chromium.org
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Reimplement basic PopularUrls page cycler in telemetry. We had a popular urls test that ran on several of the downstream bots. This test needs to be reimplemented now that the host driven test framework it used has been removed from Chromium. Implementing its base functionality here, but will need to add more such as ability to take screenshots and upload those screenshots to ISpy appengine project in the future. BUG= CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:winx64_10_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq

Patch Set 1 #

Total comments: 2

Patch Set 2 : #

Total comments: 4
Unified diffs Side-by-side diffs Delta from patch set Stats (+263 lines, -1 line) Patch
M tools/perf/benchmarks/page_cycler.py View 1 1 chunk +9 lines, -0 lines 1 comment Download
A tools/perf/page_sets/data/popular_urls.json View 1 1 chunk +115 lines, -0 lines 0 comments Download
A tools/perf/page_sets/data/popular_urls_000.wpr.sha1 View 1 1 chunk +1 line, -0 lines 0 comments Download
M tools/perf/page_sets/key_mobile_sites.py View 1 chunk +0 lines, -1 line 1 comment Download
A tools/perf/page_sets/popular_urls.py View 1 1 chunk +138 lines, -0 lines 2 comments Download

Messages

Total messages: 18 (6 generated)
mikecase (-- gone --)
I don't know if you guys had any opinions on this. Want to add add ...
4 years, 8 months ago (2016-04-20 22:04:08 UTC) #3
jbudorick
uh, wow, this is much better than before. not sure that we want/need more than ...
4 years, 8 months ago (2016-04-20 22:32:45 UTC) #4
mikecase (-- gone --)
ok, recorded a wpr for the popular urls with help from Randy. Can run the ...
4 years, 7 months ago (2016-04-28 20:49:52 UTC) #5
mikecase (-- gone --)
ping
4 years, 7 months ago (2016-05-02 17:39:35 UTC) #7
jbudorick
This seems mostly fine to me, but Ned and Randy are both more familiar with ...
4 years, 7 months ago (2016-05-02 17:46:13 UTC) #8
rnephew (Reviews Here)
On 2016/05/02 17:46:13, jbudorick wrote: > This seems mostly fine to me, but Ned and ...
4 years, 7 months ago (2016-05-02 18:01:08 UTC) #9
rnephew (Reviews Here)
On 2016/05/02 18:01:08, rnephew1 wrote: > On 2016/05/02 17:46:13, jbudorick wrote: > > This seems ...
4 years, 7 months ago (2016-05-02 18:01:25 UTC) #10
rnephew (Reviews Here)
https://codereview.chromium.org/1912443002/diff/20001/tools/perf/benchmarks/page_cycler.py File tools/perf/benchmarks/page_cycler.py (right): https://codereview.chromium.org/1912443002/diff/20001/tools/perf/benchmarks/page_cycler.py#newcode234 tools/perf/benchmarks/page_cycler.py:234: nit: 2 lines. https://codereview.chromium.org/1912443002/diff/20001/tools/perf/page_sets/popular_urls.py File tools/perf/page_sets/popular_urls.py (right): https://codereview.chromium.org/1912443002/diff/20001/tools/perf/page_sets/popular_urls.py#newcode128 tools/perf/page_sets/popular_urls.py:128: ...
4 years, 7 months ago (2016-05-02 18:02:52 UTC) #11
nednguyen
+kouhei
4 years, 7 months ago (2016-05-02 19:14:01 UTC) #13
nednguyen(REVIEW IN OTHER ACC)
On 2016/05/02 19:14:01, nednguyen (ooo til 5-4) wrote: > +kouhei Hmhh, why do you use ...
4 years, 7 months ago (2016-05-02 22:14:24 UTC) #14
mikecase (-- gone --)
On 2016/05/02 at 22:14:24, nednguyen wrote: > On 2016/05/02 19:14:01, nednguyen (ooo til 5-4) wrote: ...
4 years, 7 months ago (2016-05-09 17:05:11 UTC) #15
nednguyen
4 years, 7 months ago (2016-05-09 17:33:13 UTC) #16
On 2016/05/09 17:05:11, mikecase wrote:
> On 2016/05/02 at 22:14:24, nednguyen wrote:
> > On 2016/05/02 19:14:01, nednguyen (ooo til 5-4) wrote:
> > > +kouhei
> > 
> > Hmhh, why do you use telemetry benchmarking to migrate this to? Shouldn't
you
> use the browser_integration_test framework instead?
> 
> By browser_integration_test framework are you referring to tests like this....
?
>
https://code.google.com/p/chromium/codesearch#chromium/src/third_party/catapu...
> 
> If so, can the test runner for these tests set up WebPageReplay? 

It's possible, but we have to set up the wpr_server in setUp & tearDown
(perezju@ can show you how)

> I'm slightly
> unclear about the differences between these tests and normal telemetry tests
in
> how they are run.

The normal temeletry tests are technically not "tests", they are benchmark.
Hence their purpose is to simulate the user actions & compute some performance
metrics.

For this case, it seems to me you just want to know whether these runs are
passing/failing, hence should be using SeriallyBrowserTestCase structure
instead. It's much easier to set up for your case.

Powered by Google App Engine
This is Rietveld 408576698