Bug 177530 - [GTK] imported/w3c/web-platform-tests/XMLHttpRequest/setrequestheader-header-allowed.htm is flaky
Summary: [GTK] imported/w3c/web-platform-tests/XMLHttpRequest/setrequestheader-header-...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-27 04:35 PDT by Alicia Boya García
Modified: 2024-01-12 22:43 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 Alicia Boya García 2017-09-27 04:35:48 PDT 
imported/w3c/web-platform-tests/XMLHttpRequest/setrequestheader-header-allowed.htm is flaky on GTK.

 PASS XMLHttpRequest: setRequestHeader() - headers that are allowed (Authorization) 
-PASS XMLHttpRequest: setRequestHeader() - headers that are allowed (Pragma) 
+FAIL XMLHttpRequest: setRequestHeader() - headers that are allowed (Pragma) assert_equals: expected "Pragma," but got "pragma,"
 FAIL XMLHttpRequest: setRequestHeader() - headers that are allowed (User-Agent) assert_equals: expected "User-Agent," but got ""
 FAIL XMLHttpRequest: setRequestHeader() - headers that are allowed (Content-Transfer-Encoding) assert_equals: expected "Content-Transfer-Encoding," but got ""
 PASS XMLHttpRequest: setRequestHeader() - headers that are allowed (Content-Type) 

The problem is as old as there is data on GTK. Failure rate is quite high.

https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&revision=222541&tests=imported%2Fw3c%2Fweb-platform-tests%2FXMLHttpRequest%2Fsetrequestheader-header-allowed.htm
Comment 1 Alicia Boya García 2017-09-27 14:09:32 PDT 
Updated expectations in r222572.

Please update accordingly when this issue is resolved.
Comment 2 Diego Pino 2024-01-12 22:43:33 PST 
The test(s) filed under this bug ticket have consistently passed for the last 4000 revisions. Currently, there are no more tests in TestExpectations that refer to this bug. Therefore, I'm closing the bug.