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

Issue 875956 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Feature

Blocking:
issue 667551



Sign in to add a comment

Animations fail to complete with OOPIF layout testing

Project Member Reported by schenney@chromium.org, Aug 20

Issue description

Run a try job enabling OOPIF layout testing and look at the failures, or look at the existing try job runs.

https://chromium-review.googlesource.com/c/chromium/src/+/1075891/3


Some animations are not completing or timing out:
 virtual/threaded/animations/responsive/viewport-unit-transform-responsive.html
 virtual/threaded/animations/responsive/viewport-unit-translate-responsive.html
 virtual/threaded/animations/svg-attribute-composition/svg-startOffset-composition-003.html
 virtual/threaded/animations/timing/animation-duration-infinite.html

Fix this so we can enable OOPIF layout tests by default.
 
Blocking: 667551
Labels: Needs-Bisect
Cc: krajshree@chromium.org
Labels: Needs-Milestone Needs-Feedback Triaged-ET
schenney@ - Thanks for filing the issue...!!

Could you please provide a sample test file/url with reproducible manual steps to test the issue from TE-end. This will help us in triaging the issue further.

Thanks...!!
Labels: -Needs-Feedback -Needs-Bisect Test-Layout OS-Android OS-Chrome OS-Linux OS-Mac OS-Windows
This is purely a testing issue, we think, so there is no URL beyond the test names. The issue should be passed along to the team that fixes animation bugs. If we don't have such a team, I suppose my team can own it.

There's no bisect here. The issue is not in any Chrome release.
Labels: -Type-Bug -Pri-2 Pri-3 Type-Feature
Our process (blink triage) says Pri-3 for Features, but I agree that OOPIF testing is a bright fire.
Status: Available (was: Untriaged)
Owner: petermayo@chromium.org
Status: Assigned (was: Available)
Peter the timeouts in these tests look conceptually very similar to the failing tests in BGPT. I.e. it's failing to invoke the finished promise.

This can be reproduced locally by running with --additional-driver-flag=--site-per-process --additional-driver-flag=--enable-display-compositor-pixel-dump

Would you be able to have a look into where this is failing?

As far as I can tell, there are no frames involved.

Sign in to add a comment