New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 717538 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 575762



Sign in to add a comment

Remove or refactor repaint benchmarks into our supported harnesses

Project Member Reported by nedngu...@google.com, May 2 2017

Issue description

These repaint.* benchmarks doesn't fit into our supported harness, so we should remove them (from the perf waterfall) or refactor them. 

I think this probably also fit into blink_perf harness.

*For repaint cluster telemetry benchmark, we can move it to tools/perf/contrib directory (tracked in  issue 715704 )

 
Notes that all of these benchmarks have been failing for a while. (See https://cs.chromium.org/chromium/src/tools/perf/benchmarks/repaint.py?rcl=68557831bd0eefa24608e16f7018dc89059a9a09&l=47)

Assign to Walter for answering: "should we remove these benchmarks or try to refactor & fix them?"
 
Status: Assigned (was: Untriaged)
Labels: -Pri-3 Pri-1
Ping Walter: we are trying to clean up our benchmarks this quarter.
Cc: pdr@chromium.org chrishtr@chromium.org
I think these are old benchmarks, no longer used, and can be removed. I want to checkpoint with pdr@ and chrishtr@ to confirm before final confirmation. I have not personally looked at them, and they look to be from 2014/2015 or earlier, which predates my time on the team.

Comment 4 by pdr@chromium.org, May 9 2017

Is this for RepaintKeyMobileSites and RepaintGpuRasterizationKeyMobileSites? If so, I think it is okay to remove them.
#4: correct. RepaintCT will be moved to tools/perf/contrib (see  issue 715704 )
Cc: sullivan@chromium.org nedngu...@google.com vmi...@chromium.org
 Issue 499320  has been merged into this issue.
Status: Fixed (was: Assigned)

Sign in to add a comment