New issue
Advanced search Search tips

Issue 923177 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jan 19
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

v8.browsing_desktop/browse:social:twitter_infinite_scroll in performance_test_suite flaky on chromium.perf/mac-10_12_laptop_low_end-perf

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Jan 18 (5 days ago)

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of crouleau@google.com

loading.desktop/TheOnion_warm and 1 other(s) in performance_test_suite failing on chromium.perf/mac-10_12_laptop_low_end-perf

Builders failed on: 
- mac-10_12_laptop_low_end-perf: 
  https://ci.chromium.org/p/chrome/builders/luci.chrome.ci/mac-10_12_laptop_low_end-perf

https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=performance_test_suite&builder=chromium.perf%3Amac-10_12_laptop_low_end-perf

Passing consistently back around 620691
super flaky in 622136


 
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, Jan 18 (5 days ago)

Comment 3 by crouleau@chromium.org, Jan 18 (5 days ago)

(The above report is just used for kicking off a functional pinpoint bisect. I don't actually care about the data.)
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Jan 18 (5 days ago)

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/167e7ce2540000

Comment 5 by crouleau@chromium.org, Jan 18 (4 days ago)

Cc: simonhatch@chromium.org
FYI I think that the functional bisection could do a bit more here to help. Clearly there is a difference since it saw a difference for the first two on both sides. I will rerun the bisect with a smaller range.

Comment 6 by crouleau@chromium.org, Jan 18 (4 days ago)

Last known good: 621052

First known bad: 621142
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Jan 18 (4 days ago)

Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Jan 19 (4 days ago)

Cc: benjhayden@chromium.org
Owner: benjhayden@chromium.org
Status: Assigned (was: Available)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16aa4302540000

Ignore zeros in Breakdowns. by benjhayden@chromium.org
https://chromium.googlesource.com/catapult/+/3ad33e96e78963037240b77028d773e02d827792
Failure rate: 0 → 0.7 (+0.7)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  None

Comment 10 by benjhayden@google.com, Jan 19 (3 days ago)

Status: Fixed (was: Assigned)
That change was already reverted, so I'll close this.
https://chromium-review.googlesource.com/c/catapult/+/1419177

Sign in to add a comment