Bug 179662 - [SOUP] XHR tests with 699 status code fail
Summary: [SOUP] XHR tests with 699 status code fail
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-14 03:07 PST by Ms2ger (he/him; ⌚ UTC+1/+2)
Modified: 2019-01-10 06:35 PST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ms2ger (he/him; ⌚ UTC+1/+2) 2017-11-14 03:07:38 PST 
--- /imported/w3c/web-platform-tests/XMLHttpRequest/status-async-expected.txt
+++ /imported/w3c/web-platform-tests/XMLHttpRequest/status-async-actual.txt
@@ -23,7 +23,7 @@
 PASS XMLHttpRequest: status/statusText - various responses 22 (GET 503) 
 PASS XMLHttpRequest: status/statusText - various responses 23 (HEAD 503) 
 PASS XMLHttpRequest: status/statusText - various responses 24 (CHICKEN 503) 
-PASS XMLHttpRequest: status/statusText - various responses 25 (GET 699) 
-PASS XMLHttpRequest: status/statusText - various responses 26 (HEAD 699) 
-PASS XMLHttpRequest: status/statusText - various responses 27 (CHICKEN 699) 
+FAIL XMLHttpRequest: status/statusText - various responses 25 (GET 699) assert_equals: expected 699 but got 0
+FAIL XMLHttpRequest: status/statusText - various responses 26 (HEAD 699) assert_equals: expected 699 but got 0
+FAIL XMLHttpRequest: status/statusText - various responses 27 (CHICKEN 699) assert_equals: expected 699 but got 0
 
--- /imported/w3c/web-platform-tests/XMLHttpRequest/status-basic-expected.txt
+++ /imported/w3c/web-platform-tests/XMLHttpRequest/status-basic-actual.txt
@@ -23,7 +23,7 @@
 PASS XMLHttpRequest: status/statusText - various responses 22 (GET 503) 
 PASS XMLHttpRequest: status/statusText - various responses 23 (HEAD 503) 
 PASS XMLHttpRequest: status/statusText - various responses 24 (CHICKEN 503) 
-PASS XMLHttpRequest: status/statusText - various responses 25 (GET 699) 
-PASS XMLHttpRequest: status/statusText - various responses 26 (HEAD 699) 
-PASS XMLHttpRequest: status/statusText - various responses 27 (CHICKEN 699) 
+FAIL XMLHttpRequest: status/statusText - various responses 25 (GET 699)  A network error occurred.
+FAIL XMLHttpRequest: status/statusText - various responses 26 (HEAD 699)  A network error occurred.
+FAIL XMLHttpRequest: status/statusText - various responses 27 (CHICKEN 699)  A network error occurred.

--- /imported/w3c/web-platform-tests/XMLHttpRequest/status-error-expected.txt
+++ /imported/w3c/web-platform-tests/XMLHttpRequest/status-error-actual.txt
@@ -7,17 +7,17 @@
 PASS XMLHttpRequest: status error handling GET 404 
 PASS XMLHttpRequest: status error handling GET 410 
 PASS XMLHttpRequest: status error handling GET 500 
-PASS XMLHttpRequest: status error handling GET 699 
+FAIL XMLHttpRequest: status error handling GET 699 assert_equals: response status expected 699 but got 0
 PASS XMLHttpRequest: status error handling HEAD 200 
 PASS XMLHttpRequest: status error handling HEAD 404 
 PASS XMLHttpRequest: status error handling HEAD 500 
-PASS XMLHttpRequest: status error handling HEAD 699 
+FAIL XMLHttpRequest: status error handling HEAD 699 assert_equals: response status expected 699 but got 0
 PASS XMLHttpRequest: status error handling POST 200 
 PASS XMLHttpRequest: status error handling POST 404 
 PASS XMLHttpRequest: status error handling POST 500 
-PASS XMLHttpRequest: status error handling POST 699 
+FAIL XMLHttpRequest: status error handling POST 699 assert_equals: response status expected 699 but got 0
 PASS XMLHttpRequest: status error handling PUT 200 
 PASS XMLHttpRequest: status error handling PUT 404 
 PASS XMLHttpRequest: status error handling PUT 500 
-PASS XMLHttpRequest: status error handling PUT 699 
+FAIL XMLHttpRequest: status error handling PUT 699 assert_equals: response status expected 699 but got 0
Comment 1 Miguel Gomez 2019-01-10 06:35:19 PST 
All of them are passing since some revision between r239206 and r239377.

Updating expectations and closing bug.