RESOLVED FIXED 191424
[Mojave WK1] Layout test fast/events/detect-caps-lock.html is timing out
https://bugs.webkit.org/show_bug.cgi?id=191424
Summary [Mojave WK1] Layout test fast/events/detect-caps-lock.html is timing out
Ryan Haddad
Reported 2018-11-08 10:15:58 PST
Layout test fast/events/detect-caps-lock.html is consistently timing out on Mojave WK1 bots https://build.webkit.org/results/Apple%20Mojave%20Debug%20WK1%20(Tests)/r237886%20(543)/results.html https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=fast%2Fevents%2Fdetect-caps-lock.html --- /Volumes/Data/slave/mojave-debug-tests-wk1/build/layout-test-results/fast/events/detect-caps-lock-expected.txt +++ /Volumes/Data/slave/mojave-debug-tests-wk1/build/layout-test-results/fast/events/detect-caps-lock-actual.txt @@ -1,16 +1,6 @@ +CONSOLE MESSAGE: line 51: TypeError: testRunner.toggleCapsLock is not a function. (In 'testRunner.toggleCapsLock()', 'testRunner.toggleCapsLock' is undefined) +FAIL: Timed out waiting for notifyDone to be called This test verifies that the function WebCore::currentCapsLockState() returns true when Caps Lock is on. -1. Press Caps Lock key when view is active, make view inactive, make view active again, press Caps Lock key. -CapsLock is on. -CapsLock is not on. -2. Press Caps Lock key in inactive view, make view active, press Caps Lock key. -CapsLock is on. -CapsLock is not on. -3. Press Caps Lock key when view is active, press Caps Lock key when view is active. -CapsLock is on. -CapsLock is not on. -4. Press Caps Lock key when view is inactive, press Caps Lock key when view inactive. -CapsLock is on. -CapsLock is not on.
Attachments
Per Arne Vollan
Comment 1 2018-11-08 11:44:18 PST
This test should only run on WK2.
Ryan Haddad
Comment 2 2018-11-08 16:23:14 PST
(In reply to Per Arne Vollan from comment #1) > This test should only run on WK2. I corrected the test expectations to reflect this in https://trac.webkit.org/r238009
Radar WebKit Bug Importer
Comment 3 2018-11-08 16:24:22 PST
Note You need to log in before you can comment on or make changes to this bug.