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

Issue 2510443002: [System Health] Change scrolling behaviour for news sites. (Closed)

Created:
4 years, 1 month ago by rnephew (Reviews Here)
Modified:
4 years, 1 month ago
CC:
chromium-reviews, telemetry-reviews_chromium.org, perezju
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

[System Health] Change scrolling behaviour for news sites. They currently would wait 3 seconds, then scroll then go back to the main site. There was an issue where after scrolling, the scroll bar would constantly rewrite. This moves half the wait period to after the scrolling, so that it has time to sit idle after scrolling *** TO PERF SHERRIFS *** The change in default behaviour for the news test cases may cause regressions. These are likely not real regressions, and we just need to establish a new baseline. BUG=665220 Committed: https://crrev.com/11a42166b7ca5f2ac4ff371110d41054a2d1dc3e Cr-Commit-Position: refs/heads/master@{#432288}

Patch Set 1 #

Total comments: 2
Unified diffs Side-by-side diffs Delta from patch set Stats (+2 lines, -1 line) Patch
M tools/perf/page_sets/system_health/browsing_stories.py View 1 chunk +2 lines, -1 line 2 comments Download

Messages

Total messages: 18 (8 generated)
rnephew (Reviews Here)
4 years, 1 month ago (2016-11-15 22:07:07 UTC) #2
rnephew (Reviews Here)
https://codereview.chromium.org/2510443002/diff/1/tools/perf/page_sets/system_health/browsing_stories.py File tools/perf/page_sets/system_health/browsing_stories.py (right): https://codereview.chromium.org/2510443002/diff/1/tools/perf/page_sets/system_health/browsing_stories.py#newcode79 tools/perf/page_sets/system_health/browsing_stories.py:79: action_runner.Wait(self.ITEM_READ_TIME_IN_SECONDS/2) We could also have it wait the entire ...
4 years, 1 month ago (2016-11-15 22:08:44 UTC) #3
nednguyen
On 2016/11/15 22:07:07, rnephew (Reviews Here) wrote: lgtm Clever fix, I like this! Can you ...
4 years, 1 month ago (2016-11-15 22:09:32 UTC) #4
erikchen
lgtm
4 years, 1 month ago (2016-11-15 22:09:38 UTC) #5
rnephew (Reviews Here)
On 2016/11/15 22:09:32, nednguyen wrote: > On 2016/11/15 22:07:07, rnephew (Reviews Here) wrote: > > ...
4 years, 1 month ago (2016-11-15 22:12:39 UTC) #8
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2510443002/1
4 years, 1 month ago (2016-11-15 22:13:45 UTC) #10
commit-bot: I haz the power
Committed patchset #1 (id:1)
4 years, 1 month ago (2016-11-15 23:31:02 UTC) #13
commit-bot: I haz the power
Patchset 1 (id:??) landed as https://crrev.com/11a42166b7ca5f2ac4ff371110d41054a2d1dc3e Cr-Commit-Position: refs/heads/master@{#432288}
4 years, 1 month ago (2016-11-15 23:38:37 UTC) #15
perezju
https://codereview.chromium.org/2510443002/diff/1/tools/perf/page_sets/system_health/browsing_stories.py File tools/perf/page_sets/system_health/browsing_stories.py (right): https://codereview.chromium.org/2510443002/diff/1/tools/perf/page_sets/system_health/browsing_stories.py#newcode79 tools/perf/page_sets/system_health/browsing_stories.py:79: action_runner.Wait(self.ITEM_READ_TIME_IN_SECONDS/2) On 2016/11/15 22:08:43, rnephew (Reviews Here) wrote: > ...
4 years, 1 month ago (2016-11-16 09:58:05 UTC) #17
nednguyen
4 years, 1 month ago (2016-11-16 14:10:34 UTC) #18
Message was sent while issue was closed.
On 2016/11/16 09:58:05, perezju wrote:
>
https://codereview.chromium.org/2510443002/diff/1/tools/perf/page_sets/system...
> File tools/perf/page_sets/system_health/browsing_stories.py (right):
> 
>
https://codereview.chromium.org/2510443002/diff/1/tools/perf/page_sets/system...
> tools/perf/page_sets/system_health/browsing_stories.py:79:
> action_runner.Wait(self.ITEM_READ_TIME_IN_SECONDS/2)
> On 2016/11/15 22:08:43, rnephew (Reviews Here) wrote:
> > We could also have it wait the entire time before and after, but that will
> > increase the run time of the SH tests; but assuming my reason why we didn't
> > catch it is correct it would increase the likelihood of us catching it..
> 
> Note: This is doing integer division. So before it was waiting 3 seconds in
> total, it now waits 2 * (3 / 2) = 2 * 1 = 2 seconds!
> 
> I think what you want is:
> 
>   action_runner.Wait(self.ITEM_READ_TIME_IN_SECONDS / 2.0)

Good catch!

Powered by Google App Engine
This is Rietveld 408576698