185915 2018-05-23 07:42:23 -0700 [GTK] Suspicious warning in http/tests/xmlhttprequest/connection-error-sync.html 2018-05-24 00:40:22 -0700 1 1 1 Unclassified WebKit WebKitGTK WebKit Nightly Build Unspecified Unspecified NEW P2 Normal --- 1 aboya webkit-unassigned bugs-noreply calvaris mcatanzaro oldest_to_newest 1426571 0 aboya 2018-05-23 07:42:23 -0700 The following test has started failing on GTK in r230852:r230858: http/tests/xmlhttprequest/connection-error-sync.html This is probably a consequence of https://trac.webkit.org/changeset/230857/webkit The additional log we're getting is this: --- /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/http/tests/xmlhttprequest/connection-error-sync-expected.txt +++ /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/http/tests/xmlhttprequest/connection-error-sync-actual.txt @@ -1,3 +1,4 @@ +CONSOLE MESSAGE: line 22: XMLHttpRequest cannot load http://127.0.0.1:8000/xmlhttprequest/resources/infinite-loop.php due to access control checks. Test the behavior of a sync XMLHttpRequest that encounters an infinite redirection loop. Exception NetworkError; code=19; number=undefined (0); message=' A network error occurred.' Is that message expected? 1426841 1 mcatanzaro 2018-05-23 20:26:13 -0700 Well it's not a regression, according to Youenn's changelog: "There is a small change of behavior in the way we return an error. Instead of returning a platformBadResponseError, we are now returning the error as computed by NetworkLoadChecker. This allows getting some more error logging in the JS console." But as for whether the test is expecting its resource load to be blocked, I'm going to say no, that looks like a bug. It's frustrating that we don't know why the load was blocked. The same error occurs on tons of websites, but "access control checks" is a very vague reason. I remember talking to Alexey about this last year, we need better logging. 1426842 2 mcatanzaro 2018-05-23 20:27:09 -0700 Well, the load should be blocked, but because it is an infinite loop, not due to an access control check... right? Maybe that's an implementation detail leaking?