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

Issue 712363 link

Starred by 1 user
Status: Fixed
Owner:
panicker@chromium.org
Closed: Aug 2017
Cc:
█ briander...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Comprehensive Testing for Paint / Activation time

Project Member Reported by panicker@chromium.org, Apr 17 2017 
We are updating Paint time (for FP, FCP, FMP etc) to be the Activation time on compositor (in https://codereview.chromium.org/2778223005)
We expect to further update this to be the timestamp up to GPU swap.
If that does not end up happening we should consider beefing up automated testing for current Activation plumbing to include corner cases such as no swap happened because the tab was offscreen etc.

Brian, could you add the set of test cases you have in mind here?

Comment 1 by briander...@chromium.org, Apr 17 2017 

These aren't cases that necessarily need testing, but are cases to consider:
* output surface lost
* visibility changes
* interactions with impl-side invalidation
* multiple NotifyReadyToActivate signals before the actual activation.
* if we start measuring further down the pipeline than activation, make sure that aborts / early outs ware properly handled. e.g. when there is no damage or when the frame isn't actually consumed by a display.

Comment 2 by tdres...@chromium.org, Aug 15 2017

Owner: panicker@chromium.org
Status: Assigned (was: Available)
Who is the right owner for this?

Over to Shubhie for triage.

Comment 3 by panicker@chromium.org, Aug 15 2017

Status: Fixed (was: Assigned)
We've changed the approach since this bug was filed (using swap time) and added layout tests.
►

Sign in to add a comment