New issue
Advanced search Search tips

Issue 849859 link

Starred by 3 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Many failures in external/wpt/css/css-animations/ and web-animations/ from Mozilla tests

Project Member Reported by foolip@chromium.org, Jun 5 2018

Issue description

In https://github.com/web-platform-tests/wpt/pull/11318 Mozilla contributed tests for CSS Animations that Firefox already passes:
https://wpt.fyi/results/css/css-animations?label=experimental

These tests are currently blocking wpt-importer, which first began failing in https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/19086.

That's because results aren't the same on CQ bots as on try bots, and I'll fix that by adding failing expectations.

However, once imported there will be consistent failures as well, and triaging all of these seems highly worthwhile since they will likely reveal interoperability problems. I'm sure they'll also reveal some tests that needs changes, but hopefully that's a minority.
 
Summary: Many failures in external/wpt/css/css-animations/ from Mozilla tests (was: Many failures in external/wpt/css/css-animations/ from )
Summary: Many failures in external/wpt/css/css-animations/ and web-animations/ from Mozilla tests (was: Many failures in external/wpt/css/css-animations/ from Mozilla tests)
Based on the fact that there are so many platform-specific baselines generated by rebaseline-cl, I suspect these tests are simply flaky across the board.
Bear in mind that some of these tests cover unspecced behavior (hence the .tentative.html suffix) of features no one is yet shipping so I wouldn't be overly concerned about some of the failures. They were upstreamed at WebKit's request.

Regarding flakiness, these are running in automation for Gecko and seem to be pretty stable there, but there might be some issues regarding the timing of the first frame of the animation where we need to add some calls to `await waitForNextFrame()` to ensure we wait a full frame.
Cc: flackr@chromium.org
Status: Available (was: Untriaged)
Sounds like we should get on to figuring out how to deal with this soon, flackr@ ?
Labels: Hotlist-Interop

Sign in to add a comment