Bug 161742 - REGRESSION: [mac-wk2 debug] LayoutTest imported/w3c/web-platform-tests/IndexedDB/keyorder.htm is a flaky failure
Summary: REGRESSION: [mac-wk2 debug] LayoutTest imported/w3c/web-platform-tests/Indexe...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 154968
  Show dependency treegraph
 
Reported: 2016-09-08 10:04 PDT by Ryan Haddad
Modified: 2016-12-02 10:49 PST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Haddad 2016-09-08 10:04:01 PDT
REGRESSION: LayoutTest imported/w3c/web-platform-tests/IndexedDB/keyorder.htm is a flaky failure

https://build.webkit.org/builders/Apple%20El%20Capitan%20Debug%20WK2%20(Tests)/builds/8053

https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=imported%2Fw3c%2Fweb-platform-tests%2FIndexedDB%2Fkeyorder.htm

--- /Volumes/Data/slave/elcapitan-debug-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/IndexedDB/keyorder-expected.txt
+++ /Volumes/Data/slave/elcapitan-debug-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/IndexedDB/keyorder-actual.txt
@@ -1,26 +1,26 @@
 
-PASS Database readback sort - String < Array 
+TIMEOUT Database readback sort - String < Array Test timed out
 PASS IDBKey.cmp sorted - String < Array 
-PASS Database readback sort - float < String 
+TIMEOUT Database readback sort - float < String Test timed out
 PASS IDBKey.cmp sorted - float < String 
-PASS Database readback sort - float < Date 
+TIMEOUT Database readback sort - float < Date Test timed out
 PASS IDBKey.cmp sorted - float < Date 
-PASS Database readback sort - float < Date < String < Array 
+TIMEOUT Database readback sort - float < Date < String < Array Test timed out
 PASS IDBKey.cmp sorted - float < Date < String < Array 
-PASS Database readback sort - Date(1 sec ago) < Date(now) < Date(1 minute in future) 
+TIMEOUT Database readback sort - Date(1 sec ago) < Date(now) < Date(1 minute in future) Test timed out
 PASS IDBKey.cmp sorted - Date(1 sec ago) < Date(now) < Date(1 minute in future) 
-PASS Database readback sort - -1.1 < 1 < 1.01337 < 1.013373 < 2 
+TIMEOUT Database readback sort - -1.1 < 1 < 1.01337 < 1.013373 < 2 Test timed out
 PASS IDBKey.cmp sorted - -1.1 < 1 < 1.01337 < 1.013373 < 2 
-PASS Database readback sort - -Infinity < -0.01 < 0 < Infinity 
+TIMEOUT Database readback sort - -Infinity < -0.01 < 0 < Infinity Test timed out
 PASS IDBKey.cmp sorted - -Infinity < -0.01 < 0 < Infinity 
-PASS Database readback sort - "" < "a" < "ab" < "b" < "ba" 
+TIMEOUT Database readback sort - "" < "a" < "ab" < "b" < "ba" Test timed out
 PASS IDBKey.cmp sorted - "" < "a" < "ab" < "b" < "ba" 
-PASS Database readback sort - Arrays 
+TIMEOUT Database readback sort - Arrays Test timed out
 PASS IDBKey.cmp sorted - Arrays 
-PASS Database readback sort - Array.length: 10,000 < Array.length: 10,001 
+TIMEOUT Database readback sort - Array.length: 10,000 < Array.length: 10,001 Test timed out
 PASS IDBKey.cmp sorted - Array.length: 10,000 < Array.length: 10,001 
-PASS Database readback sort - Infinity inside arrays 
+TIMEOUT Database readback sort - Infinity inside arrays Test timed out
 PASS IDBKey.cmp sorted - Infinity inside arrays 
-PASS Database readback sort - Test different stuff at once 
+TIMEOUT Database readback sort - Test different stuff at once Test timed out
 PASS IDBKey.cmp sorted - Test different stuff at once
Comment 1 Ryan Haddad 2016-09-08 10:05:49 PDT
The first failure according to the dashboard was a test run with https://trac.webkit.org/log/?verbose=on&rev=204839&stop_rev=204832

Since it is a flaky failure, those revisions may not include the actual regression point.
Comment 2 Ryan Haddad 2016-09-09 10:00:07 PDT
Marked test as flaky in http://trac.webkit.org/projects/webkit/changeset/205748
Comment 3 Brady Eidson 2016-12-02 10:49:48 PST
Every remotely recent failure on the flakiness dashboard is due to a much more systemic problem:

Either the w3c platform test server crashing, or due to file handle leaks causing *all* tests to start failing.

I don't think this has legitimately been flaking for some time - Probably since my massive key-serialization performance improvements.