Bug 177214 - Layout test imported/w3c/web-platform-tests/FileAPI/historical.https.html is flaky.
Summary: Layout test imported/w3c/web-platform-tests/FileAPI/historical.https.html is ...
Status: RESOLVED CONFIGURATION CHANGED
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: InRadar
Depends on:
Blocks:
 
Reported: 2017-09-19 18:32 PDT by Matt Lewis
Modified: 2020-01-31 07:43 PST (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Lewis 2017-09-19 18:32:04 PDT
imported/w3c/web-platform-tests/FileAPI/historical.https.html is a flaky failure on El Capitan WK2 Debug according to the flakiness dashboard:

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

recent build:
https://build.webkit.org/results/Apple%20El%20Capitan%20Debug%20WK2%20(Tests)/r222228%20(3163)/results.html


diff:

--- /Volumes/Data/slave/elcapitan-debug-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/FileAPI/historical.https-expected.txt
+++ /Volumes/Data/slave/elcapitan-debug-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/FileAPI/historical.https-actual.txt
@@ -1,3 +1,4 @@
+CONSOLE MESSAGE: line 153: TypeError: undefined is not an object (evaluating 'registration.unregister')
 
 PASS "toNativeLineEndings" should not be supported 
 FAIL "FileError" should not be supported assert_false: expected false got true
Comment 1 Ryan Haddad 2017-09-21 13:45:45 PDT
Marked test as flaky in https://trac.webkit.org/changeset/222347/webkit
Comment 2 Joseph Pecoraro 2018-08-09 17:09:43 PDT
Closing. El Capitan expectations have been removed and this was an El Capitan specific failure / expectation.
Comment 3 Radar WebKit Bug Importer 2018-08-09 17:10:35 PDT
<rdar://problem/43118311>
Comment 4 Jason Lawrence 2020-01-31 07:43:15 PST
I could not reproduce this issue using run-webkit-test iterations on build 255462 or 251589.