Perma Beta TEST-UNEXPECTED-ERROR | /css/css-lists/animations/list-style-image-interpolation.html | NotSupportedError: Animation to or from an underlying value is not yet supported. when Gecko 73 merges to Beta on 2020-01-06
Categories
(Core :: Layout: Generated Content, Lists, and Counters, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox71 | --- | unaffected |
firefox72 | --- | unaffected |
firefox73 | + | verified |
People
(Reporter: malexandru, Assigned: daisuke)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
Central as Beta simulation: https://treeherder.mozilla.org/#/jobs?repo=try&group_state=expanded&selectedJob=279761580&resultStatus=testfailed%2Cbusted%2Cexception%2Crunnable&revision=aecfd7f620754519683b9048d3832982688498c0&searchStr=%28wpt
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=279762826&repo=try&lineNumber=3485
[task 2019-12-05T12:03:01.886Z] 12:03:01 INFO - TEST-OK | /css/css-images/gradient/color-stops-parsing.html | took 1377ms
[task 2019-12-05T12:03:01.887Z] 12:03:01 INFO - TEST-START | /css/css-lists/animations/list-style-image-interpolation.html
[task 2019-12-05T12:03:01.914Z] 12:03:01 INFO - Closing window 130
[task 2019-12-05T12:03:03.231Z] 12:03:03 INFO - TEST-UNEXPECTED-ERROR | /css/css-lists/animations/list-style-image-interpolation.html | NotSupportedError: Animation to or from an underlying value is not yet supported.
[task 2019-12-05T12:03:03.231Z] 12:03:03 INFO - interpolateComposite@http://web-platform.test:8000/css/support/interpolation-testcommon.js:135:30
[task 2019-12-05T12:03:03.231Z] 12:03:03 INFO - interpolate@http://web-platform.test:8000/css/support/interpolation-testcommon.js:100:12
[task 2019-12-05T12:03:03.231Z] 12:03:03 INFO - createInterpolationTestTargets/</target.interpolate@http://web-platform.test:8000/css/support/interpolation-testcommon.js:278:29
[task 2019-12-05T12:03:03.231Z] 12:03:03 INFO - test_interpolation@http://web-platform.test:8000/css/support/interpolation-testcommon.js:331:14
[task 2019-12-05T12:03:03.231Z] 12:03:03 INFO - @http://web-platform.test:8000/css/css-lists/animations/list-style-image-interpolation.html:32:19
[task 2019-12-05T12:03:03.231Z] 12:03:03 INFO - TEST-INFO took 1340ms
James, can you please take a look at this?
Looks to be from Bug 1599869
![]() |
||
Comment 1•6 years ago
|
||
Only occurs on slowish platform (Linux asan and debug, Android). Daisuke, do you know if this an issue with the build performance or does a preference need to be set? If it's the latter, is it dom.animations-api.compositing.enabled
? Thank you in advance.
Updated•6 years ago
|
Assignee | ||
Comment 2•6 years ago
|
||
Hello, I'm sorry for my delay.
I don't think dom.animations-api.compositing.enabled
pref is related to this bug.
Usually, this failure occured in case dom.animations-api.implicit-keyframes.enabled
is false.
However, we turned the pref on at https://phabricator.services.mozilla.com/D47034#change-eK4UBF5kg5qo for web-platform testing.
I don't know why the pref is not applied only for this test yet.
Let me take a look.
Updated•6 years ago
|
Comment 3•6 years ago
|
||
Changing the priority to p2 as the bug is tracked by a release manager for the current nightly.
See What Do You Triage for more information
Updated•6 years ago
|
Comment 4•6 years ago
|
||
If we're expecting a code fix here, I'm going to clear my needinfo, because :daisuke will do a better job than me :) But feel free to re-needinfo me if we decide to just update the metadata to clear the permafail.
Comment 5•6 years ago
|
||
Daisuke and I looked at this but so far we have no idea what is going on. dom.animations-api.implicit-keyframes.enabled
should be set via the webplatform tests user.js
but doesn't seem to be. If you know of any cases where that doesn't happen, or doesn't happen immediately, especially on slower platforms, that would be very useful information!
Comment 6•6 years ago
•
|
||
If you're setting it in a user.js file it ought to end up in the profile, which seems to rule out the possibility of races or similar. You could also try setting it in the relevant __dir__.ini
which uses a different codepath.
Updated•6 years ago
|
Comment 7•6 years ago
|
||
(In reply to James Graham [:jgraham] from comment #6)
If you're setting it in a user.js file it ought to end up in the profile, which seems to rule out the possibility of races or similar. You could also try setting it in the relevant
__dir__.ini
which uses a different codepath.
Daisuke, can you try that to see if it helps?
Assignee | ||
Comment 8•6 years ago
|
||
Yep! Try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=065a0d5b991c23049d3dd2bc50005a3ca536e8b8
Assignee | ||
Comment 9•6 years ago
|
||
Assignee | ||
Comment 10•6 years ago
|
||
Sorry, I have mistaken the base of patches I threw to the try-server.
try again: https://treeherder.mozilla.org/#/jobs?repo=try&revision=f2cd019ed32e5e9b4e2d471f3899b95f547dc2b9
Comment 11•6 years ago
|
||
(In reply to Daisuke Akatsuka (:daisuke) from comment #10)
Sorry, I have mistaken the base of patches I threw to the try-server.
try again: https://treeherder.mozilla.org/#/jobs?repo=try&revision=f2cd019ed32e5e9b4e2d471f3899b95f547dc2b9
All failures are know intermittent or other expected fails. This failure does not occur on your try push.
Comment 12•6 years ago
|
||
Imported the patch and issue seems to be fixed.
Comment 13•6 years ago
|
||
I can confirm that these failures did not show up in today's beta sim:
https://treeherder.mozilla.org/#/jobs?repo=try&selectedJob=281258946&revision=e8bbb8ced33e292699b3fb006978b2fc4d6fe92d&searchStr=android%2C7.0%2Cx86-64%2Cdebug%2Cweb%2Cplatform%2Ctests%2Ctest-android-em-7.0-x86_64%2Fdebug-geckoview-web-platform-tests-e10s-18%2Cw%28wpt18%29
Comment 14•6 years ago
|
||
It's really odd that this fixes it. For the failure itself, I think there are roughly three likely causes:
- The pref is not working properly.
- The pref is not being applied properly by
user.js
. - The pref is being applied properly by
user.js
but then somehow being reset/cleared etc.
I think we can eliminate (1) since the patch seems to prove the pref works.
I couldn't find any other tests resetting this pref in WPT (unless something does it globally?) so I'm inclined to think it's (2) and there is something amiss with the interaction between setting up profiles and the wpt test runner.
There are two instances in mochitests where we reset these prefs but presumably those use a different profile and instance of Firefox?
Comment 15•6 years ago
|
||
Comment 16•6 years ago
|
||
bugherder |
Comment 17•6 years ago
|
||
Updated•6 years ago
|
Description
•