WebKit Bugzilla
Attachment 368752 Details for
Bug 197473
: REGRESSION: Layout test imported/w3c/web-platform-tests/resource-timing/resource-timing-level1.sub.html is frequently failing on EWS
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
Remember
[x]
|
Forgot Password
Login:
[x]
[patch]
Patch
bug-197473-20190501194215.patch (text/plain), 6.49 KB, created by
youenn fablet
on 2019-05-01 19:42:16 PDT
(
hide
)
Description:
Patch
Filename:
MIME Type:
Creator:
youenn fablet
Created:
2019-05-01 19:42:16 PDT
Size:
6.49 KB
patch
obsolete
>Subversion Revision: 244802 >diff --git a/LayoutTests/ChangeLog b/LayoutTests/ChangeLog >index 4c834ad04ed7c92f29cda19a7ed18c6f2284c015..4aecc5cee444dc82f64a7a85c88a6d1fa50dad2d 100644 >--- a/LayoutTests/ChangeLog >+++ b/LayoutTests/ChangeLog >@@ -1,3 +1,14 @@ >+2019-05-01 Youenn Fablet <youenn@apple.com> >+ >+ REGRESSION: Layout test imported/w3c/web-platform-tests/resource-timing/resource-timing-level1.sub.html is frequently failing on Mac-ews >+ https://bugs.webkit.org/show_bug.cgi?id=197473 >+ >+ Unreviewed. >+ >+ Mark test as slow. >+ >+ * TestExpectations: >+ > 2019-05-01 Youenn Fablet <youenn@apple.com> > > Cache.add and Cache.addAll should compute a correct response body size >diff --git a/LayoutTests/imported/w3c/ChangeLog b/LayoutTests/imported/w3c/ChangeLog >index d7ad0751174cbdb6d5549bdf38f1f7186105b147..0edd4891850c9bee84b713eac04b49eea3c6468e 100644 >--- a/LayoutTests/imported/w3c/ChangeLog >+++ b/LayoutTests/imported/w3c/ChangeLog >@@ -1,3 +1,12 @@ >+2019-05-01 Youenn Fablet <youenn@apple.com> >+ >+ REGRESSION: Layout test imported/w3c/web-platform-tests/resource-timing/resource-timing-level1.sub.html is frequently failing on Mac-ews >+ https://bugs.webkit.org/show_bug.cgi?id=197473 >+ >+ Unreviewed, rebasing test. >+ >+ * web-platform-tests/resource-timing/resource-timing-level1.sub-expected.txt: >+ > 2019-05-01 Youenn Fablet <youenn@apple.com> > > LayoutTest imported/w3c/web-platform-tests/xhr/event-upload-progress-crossorigin.htm is a flaky failure >diff --git a/LayoutTests/TestExpectations b/LayoutTests/TestExpectations >index e502f29b49dccdcc5ceaef64daf9d6335c61ac00..f07f49c0dfa0f14a5da7528b899e98ce433fd208 100644 >--- a/LayoutTests/TestExpectations >+++ b/LayoutTests/TestExpectations >@@ -286,6 +286,8 @@ imported/w3c/web-platform-tests/service-workers/service-worker/fetch-request-res > [ Debug ] imported/w3c/web-platform-tests/service-workers/service-worker/registration-mime-types.https.html [ Slow ] > [ Debug ] imported/w3c/web-platform-tests/service-workers/service-worker/redirected-response.https.html [ Slow ] > >+imported/w3c/web-platform-tests/resource-timing/resource-timing-level1.sub.html [ Slow ] >+ > # Reenable it when having a custom gc exposed in service workers. > [ Debug ] http/wpt/service-workers/fetchEvent.https.html [ Skip ] > >diff --git a/LayoutTests/imported/w3c/web-platform-tests/resource-timing/resource-timing-level1.sub-expected.txt b/LayoutTests/imported/w3c/web-platform-tests/resource-timing/resource-timing-level1.sub-expected.txt >index 5ce703a3f84a4089a304cd6cf046bd68eb90124e..e6837222a8990f8b1c2f56c06318d08c5b7d86f9 100644 >--- a/LayoutTests/imported/w3c/web-platform-tests/resource-timing/resource-timing-level1.sub-expected.txt >+++ b/LayoutTests/imported/w3c/web-platform-tests/resource-timing/resource-timing-level1.sub-expected.txt >@@ -1,11 +1,27 @@ > >-Harness Error (TIMEOUT), message = null >- > PASS No timeline entry for about:blank > PASS 'iframe (Populate cache): The initial request populates the cache (if appropriate). > PASS 'iframe (Potentially Cached): Immediately fetch the same URL, exercising the cache hit path (if any). > PASS 'xmlhttprequest (Populate cache): The initial request populates the cache (if appropriate). > PASS 'xmlhttprequest (Potentially Cached): Immediately fetch the same URL, exercising the cache hit path (if any). >-TIMEOUT 'script (Populate cache): The initial request populates the cache (if appropriate). Test timed out >-TIMEOUT 'script (Potentially Cached): Immediately fetch the same URL, exercising the cache hit path (if any). Test timed out >+PASS 'script (Populate cache): The initial request populates the cache (if appropriate). >+PASS 'script (Potentially Cached): Immediately fetch the same URL, exercising the cache hit path (if any). >+PASS 'link (Populate cache): The initial request populates the cache (if appropriate). >+PASS 'link (Potentially Cached): Immediately fetch the same URL, exercising the cache hit path (if any). >+PASS 'iframe: 250ms delay before 'responseStart', another 250ms delay before 'responseEnd'. >+PASS 'xmlhttprequest: 250ms delay before 'responseStart', another 250ms delay before 'responseEnd'. >+PASS 'script: 250ms delay before 'responseStart', another 250ms delay before 'responseEnd'. >+PASS 'link: 250ms delay before 'responseStart', another 250ms delay before 'responseEnd'. >+PASS 'iframe (Redirected): 250ms delay before 'redirectEnd', another 250ms delay before 'responseStart'. >+PASS 'xmlhttprequest (Redirected): 250ms delay before 'redirectEnd', another 250ms delay before 'responseStart'. >+PASS 'script (Redirected): 250ms delay before 'redirectEnd', another 250ms delay before 'responseStart'. >+PASS 'link (Redirected): 250ms delay before 'redirectEnd', another 250ms delay before 'responseStart'. >+FAIL 'iframe 250ms delay in headers does not affect responseStart' assert_greater_than_equal: Delay after HTTP/1.1 status should not affect 'responseStart'. expected a number greater than or equal to 9243 but got 8993 >+FAIL 'xmlhttprequest 250ms delay in headers does not affect responseStart' assert_greater_than_equal: Delay after HTTP/1.1 status should not affect 'responseStart'. expected a number greater than or equal to 9758 but got 9509 >+FAIL 'script 250ms delay in headers does not affect responseStart' assert_greater_than_equal: Delay after HTTP/1.1 status should not affect 'responseStart'. expected a number greater than or equal to 10251 but got 10002 >+FAIL 'link 250ms delay in headers does not affect responseStart' assert_greater_than_equal: Delay after HTTP/1.1 status should not affect 'responseStart'. expected a number greater than or equal to 10747 but got 10498 >+FAIL 'iframe responseStart uses 1XX (first) response timings' assert_greater_than_equal: HTTP/1.1 1XX (first) response should determine 'responseStart' timing. expected a number greater than or equal to 11308 but got 11059.000000000002 >+FAIL 'xmlhttprequest responseStart uses 1XX (first) response timings' assert_greater_than_equal: HTTP/1.1 1XX (first) response should determine 'responseStart' timing. expected a number greater than or equal to 11810 but got 11561 >+FAIL 'script responseStart uses 1XX (first) response timings' assert_greater_than_equal: HTTP/1.1 1XX (first) response should determine 'responseStart' timing. expected a number greater than or equal to 12297 but got 12047 >+FAIL 'link responseStart uses 1XX (first) response timings' assert_greater_than_equal: HTTP/1.1 1XX (first) response should determine 'responseStart' timing. expected a number greater than or equal to 12788 but got 12539 > Show details
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Flags:
ews-watchlist
:
commit-queue-
Actions:
View
|
Formatted Diff
|
Diff
Attachments on
bug 197473
: 368752 |
368759
|
368791