RESOLVED DUPLICATE of bug 63904 Bug 63910
[Qt] http/tests/inspector/network-preflight-options.html fails frequently
https://bugs.webkit.org/show_bug.cgi?id=63910
Summary [Qt] http/tests/inspector/network-preflight-options.html fails frequently
Andras Becsi
Reported 2011-07-04 08:13:58 PDT
Most of the time http/tests/inspector/network-preflight-options.html fails with the wrong sequence of POST messages, even though sporadically the test passes. --- /ramdisk/qt-linux-release/build/layout-test-results/http/tests/inspector/network-preflight-options-expected.txt 2011-07-04 07:31:47.371328429 -0700 +++ /ramdisk/qt-linux-release/build/layout-test-results/http/tests/inspector/network-preflight-options-actual.txt 2011-07-04 07:31:47.371328429 -0700 @@ -8,8 +8,8 @@ OPTIONS http://localhost:8000/inspector/resources/cors-target.php?deny=yes OPTIONS http://localhost:8000/inspector/resources/cors-target.php POST http://localhost:8000/inspector/resources/cors-target.php -POST http://localhost:8000/inspector/resources/cors-target.php?deny=yes OPTIONS http://localhost:8000/inspector/resources/cors-target.php?deny=yes +POST http://localhost:8000/inspector/resources/cors-target.php?deny=yes OPTIONS http://localhost:8000/inspector/resources/cors-target.php?async=yes POST http://localhost:8000/inspector/resources/cors-target.php?async=yes Console does not give much help on when the failing started, it might be caused during the weekend after the 1st of July.
Attachments
Andras Becsi
Comment 1 2011-07-04 08:27:07 PDT
(In reply to comment #0) > Console does not give much help on when the failing started, it might be caused during the weekend after the 1st of July. The regression was most probably intorduced by Web Inspector: Preflight OPTIONS requests are not shown on network panel for asynchronous XHRs. http://trac.webkit.org/changeset/90340 I'm going to skip the test on the Qt bot.
Andras Becsi
Comment 2 2011-07-04 08:32:45 PDT
Vsevolod Vlasov
Comment 3 2011-07-04 08:53:45 PDT
*** This bug has been marked as a duplicate of bug 63904 ***
Note You need to log in before you can comment on or make changes to this bug.