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

Issue 1921633003: [Telemetry] Rename page_test to legacy_page_test (Closed)

Created:
4 years, 8 months ago by nednguyen
Modified:
4 years, 8 months ago
CC:
catapult-reviews_chromium.org, telemetry-reviews_chromium.org
Base URL:
https://github.com/catapult-project/catapult@master
Target Ref:
refs/heads/master
Project:
catapult
Visibility:
Public.

Description

[Telemetry] Rename page_test to legacy_page_test This is to make it clearer for telemetry users that TBMV2 is the way to write a new performance benchmarks. After all the sites in chromium/src is updated to reference legacy_page_test.LegacyPageTest (crbug.com/606643), I will remove the shim. BUG=catapult:#2218 Committed: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+/254b0aa0b9c710ff983d3256433543f58ac2db15

Patch Set 1 #

Patch Set 2 : Add TODO #

Unified diffs Side-by-side diffs Delta from patch set Stats (+85 lines, -249 lines) Patch
M telemetry/telemetry/benchmark.py View 2 chunks +2 lines, -2 lines 0 comments Download
M telemetry/telemetry/benchmark_run_unittest.py View 1 chunk +2 lines, -2 lines 0 comments Download
M telemetry/telemetry/benchmark_unittest.py View 1 chunk +2 lines, -2 lines 0 comments Download
M telemetry/telemetry/internal/story_runner.py View 3 chunks +3 lines, -3 lines 0 comments Download
M telemetry/telemetry/internal/story_runner_unittest.py View 7 chunks +7 lines, -7 lines 0 comments Download
A + telemetry/telemetry/page/legacy_page_test.py View 5 chunks +17 lines, -8 lines 0 comments Download
M telemetry/telemetry/page/page_run_end_to_end_unittest.py View 17 chunks +18 lines, -18 lines 0 comments Download
M telemetry/telemetry/page/page_test.py View 1 1 chunk +4 lines, -177 lines 0 comments Download
M telemetry/telemetry/page/page_test_unittest.py View 4 chunks +13 lines, -13 lines 0 comments Download
M telemetry/telemetry/page/shared_page_state.py View 3 chunks +3 lines, -3 lines 0 comments Download
M telemetry/telemetry/page/shared_page_state_unittest.py View 2 chunks +2 lines, -2 lines 0 comments Download
M telemetry/telemetry/record_wpr.py View 1 chunk +2 lines, -2 lines 0 comments Download
M telemetry/telemetry/record_wpr_unittest.py View 2 chunks +2 lines, -2 lines 0 comments Download
M telemetry/telemetry/story/shared_state.py View 1 chunk +1 line, -1 line 0 comments Download
M telemetry/telemetry/testing/page_test_test_case.py View 3 chunks +3 lines, -3 lines 0 comments Download
M telemetry/telemetry/web_perf/smooth_gesture_util_unittest.py View 2 chunks +2 lines, -2 lines 0 comments Download
M telemetry/telemetry/web_perf/timeline_based_page_test.py View 1 chunk +2 lines, -2 lines 0 comments Download

Messages

Total messages: 10 (4 generated)
nednguyen
FWIW, I takes this clean up as urgent because the service worker team in Tokyo ...
4 years, 8 months ago (2016-04-26 03:39:44 UTC) #2
eakuefner
lgtm, and thanks for taking this on -- just be wary of chromium-side modifications that ...
4 years, 8 months ago (2016-04-26 05:07:28 UTC) #4
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1921633003/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1921633003/20001
4 years, 8 months ago (2016-04-26 05:26:03 UTC) #6
nednguyen
On 2016/04/26 05:07:28, eakuefner (OOO until Apr 25) wrote: > lgtm, and thanks for taking ...
4 years, 8 months ago (2016-04-26 05:26:20 UTC) #7
commit-bot: I haz the power
Committed patchset #2 (id:20001) as https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+/254b0aa0b9c710ff983d3256433543f58ac2db15
4 years, 8 months ago (2016-04-26 05:46:43 UTC) #9
eakuefner
4 years, 8 months ago (2016-04-26 05:49:20 UTC) #10
Message was sent while issue was closed.
On 2016/04/26 at 05:26:20, nednguyen wrote:
> On 2016/04/26 05:07:28, eakuefner (OOO until Apr 25) wrote:
> > lgtm, and thanks for taking this on -- just be wary of chromium-side
> > modifications that may or may not need to be done.
> 
> What do you mean that "may not need to be done?"

Sorry, just meant that if there are any references to page_test in Chromium that
would need to be taken account, but was too lazy to look into it myself.

Powered by Google App Engine
This is Rietveld 408576698