[ BigSur wk2 Debug ] http/tests/inspector/network/resource-request-headers.html is flaky failing

• Component: Web Inspector
• Status: NEW ---

http/tests/inspector/network/resource-request-headers.html

Is a flaky failure on BigSur wk2 Debug.

History: https://results.webkit.org/?suite=layout-tests&test=http%2Ftests%2Finspector%2Fnetwork%2Fresource-request-headers.html

The test has been marked to fail on Mac wk1 at https://trac.webkit.org/changeset/215062/webkit.

The flaky failure on BigSur wk2 Debug is relatively recently according to the history with the fist failure seen at r280244. 

Result page: https://build.webkit.org/results/Apple-BigSur-Debug-WK2-Tests/r282142%20(3644)/results.html

Diff: 

--- /Volumes/Data/worker/bigsur-debug-tests-wk2/build/layout-test-results/http/tests/inspector/network/resource-request-headers-expected.txt
+++ /Volumes/Data/worker/bigsur-debug-tests-wk2/build/layout-test-results/http/tests/inspector/network/resource-request-headers-actual.txt
@@ -15,24 +15,37 @@
 PASS: 'Cookie' header value should be `InspectorTestCookie=1234`.
 
 -- Running test case: Resource.Metrics.RequestHeaders.BasicAuth.None
-PASS: Resource should be created.
-PASS: Resource should receive a Response.
-PASS: Resource should have a 401 status code.
-PASS: Response should have a 'WWW-Authenticate' response header for the failure.
-PASS: Request should not have a 'Authorization' header.
+!! TIMEOUT: took longer than 10000ms
 
 -- Running test case: Resource.Metrics.RequestHeaders.BasicAuth.Failure
 PASS: Resource should be created.
 PASS: Resource should receive a Response.
 PASS: Resource should have a 401 status code.
 PASS: Response should have a 'WWW-Authenticate' response header for the failure.
+PASS: Request should not have a 'Authorization' header.
+PASS: Resource should be created.
+FAIL: Resource should receive a Response.
+    Expected: Resource instance #2
+    Actual: Resource instance #1
+FAIL: Resource should have a 401 status code.
+    Expected: 401
+    Actual: NaN
+FAIL: Response should have a 'WWW-Authenticate' response header for the failure.
+    Expected: truthy
+    Actual: undefined
 FAIL: 'Authorization' header value should be for badUsername:badPassword.
     Expected: "Basic YmFkVXNlcm5hbWU6YmFkUGFzc3dvcmQ="
     Actual: undefined
 
 -- Running test case: Resource.Metrics.RequestHeaders.BasicAuth.Success
 PASS: Resource should be created.
-PASS: Resource should receive a Response.
-PASS: Resource should have a 200 status code.
-PASS: 'Authorization' header value should be for goodUsername:goodPassword.
+FAIL: Resource should receive a Response.
+    Expected: Resource instance #1
+    Actual: Resource instance #3
+FAIL: Resource should have a 200 status code.
+    Expected: 200
+    Actual: NaN
+FAIL: 'Authorization' header value should be for goodUsername:goodPassword.
+    Expected: "Basic Z29vZFVzZXJuYW1lOmdvb2RQYXNzd29yZA=="
+    Actual: undefined

[Radar WebKit Bug Importer]

<rdar://problem/82883922>

Marked test expectations https://trac.webkit.org/changeset/282161/webkit

[Eric Hutchison]

http/tests/inspector/network/har/har-page-aggressive-gc.html is also affected: History : https://results.webkit.org/?suite=layout-tests&test=http%2Ftests%2Finspector%2Fnetwork%2Fhar%2Fhar-page-aggressive-gc.html&platform=mac

[Eric Hutchison]

Updated test expectations at https://trac.webkit.org/changeset/282231/webkit.