Bug 188219 - [GTK] legacy-animation-engine/animations/animation-direction-normal.html is flaky
Summary: [GTK] legacy-animation-engine/animations/animation-direction-normal.html is f...
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-01 04:14 PDT by Alicia Boya García
Modified: 2020-03-09 12:58 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alicia Boya García 2018-08-01 04:14:24 PDT 
The following test is flaky on GTK since r234345 or earlier.

legacy-animation-engine/animations/animation-direction-normal.html

--- /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/legacy-animation-engine/animations/animation-direction-normal-expected.txt
+++ /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/legacy-animation-engine/animations/animation-direction-normal-actual.txt
@@ -1,4 +1,4 @@
-PASS - "webkitTransform" property for "box" element at 0.5s saw something close to: 1,0,0,1,50,0
-PASS - "webkitTransform" property for "box" element at 1s saw something close to: 1,0,0,1,100,0
-PASS - "webkitTransform" property for "box" element at 2.5s saw something close to: 1,0,0,1,50,0
+FAIL - "webkitTransform" property for "box" element at 0.5s expected: 1,0,0,1,50,0 but saw: matrix(1, 0, 0, 1, 81.90299987792969, 0)
+FAIL - "webkitTransform" property for "box" element at 1s expected: 1,0,0,1,100,0 but saw: matrix(1, 0, 0, 1, 131.7631072998047, 0)
+FAIL - "webkitTransform" property for "box" element at 2.5s expected: 1,0,0,1,50,0 but saw: matrix(1, 0, 0, 1, 81.80819702148438, 0)

The issue does not reproduce in the Wayland bot.
Comment 1 Antoine Quint 2020-03-09 12:58:06 PDT 
This test is gone as of r258150, see bug 208815.