Bug 91366

Summary: [EFL] fast/forms/number/spin-button-gets-disabled-or-readonly.html is flaky
Product: WebKit Reporter: Chris Dumez <cdumez>
Component: WebKit EFLAssignee: Jussi Kukkonen (jku) <jussi.kukkonen>
Status: RESOLVED WONTFIX    
Severity: Normal CC: gyuyoung.kim, jussi.kukkonen, lucas.de.marchi, mcatanzaro, sw0524.lee, tmpsantos
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   

Chris Dumez
Reported 2012-07-16 00:55:17 PDT
fast/forms/number/spin-button-gets-disabled-or-readonly.html is flaky on the build bot: --- /home/buildslave-1/webkit-buildslave/efl-linux-64-debug/build/layout-test-results/fast/forms/number/spin-button-gets-disabled-or-readonly-expected.txt +++ /home/buildslave-1/webkit-buildslave/efl-linux-64-debug/build/layout-test-results/fast/forms/number/spin-button-gets-disabled-or-readonly-actual.txt @@ -10,17 +10,17 @@ delay = 1 ms PASS input.value is "1234566" delay = 10 ms -PASS input.value is "1234566" +FAIL input.value should be 1234566. Was 1234567. delay = 100 ms -PASS input.value is "1234566" +FAIL input.value should be 1234566. Was 1234567. Test on a disabled number input form: delay = 1 ms PASS input.value is "1234566" delay = 10 ms -PASS input.value is "1234566" +FAIL input.value should be 1234566. Was 1234567. delay = 100 ms -PASS input.value is "1234566" +FAIL input.value should be 1234566. Was 1234567. PASS successfullyParsed is true TEST COMPLETE
Attachments
Jussi Kukkonen (jku)
Comment 1 2012-11-26 05:33:14 PST
First results from the find-flakiness-source frankenstein script: Running these in the same worker fast/events/touch/emulate-touch-events.html fast/forms/number/number-spinbutton-gets-disabled-or-readonly.html always makes the latter fail.
Michael Catanzaro
Comment 2 2017-03-11 10:52:38 PST
Closing this bug because the EFL port has been removed from trunk. If you feel this bug applies to a different upstream WebKit port and was closed in error, please either update the title and reopen the bug, or leave a comment to request this.
Note You need to log in before you can comment on or make changes to this bug.