RESOLVED DUPLICATE of bug 124566268896
[Win] fast/dom/SelectorAPI/resig-SelectorsAPI-test.xhtml is timing out after WebKitRequirements v2024.02.05
https://bugs.webkit.org/show_bug.cgi?id=268896
Summary [Win] fast/dom/SelectorAPI/resig-SelectorsAPI-test.xhtml is timing out after ...
Fujii Hironori
Reported 2024-02-06 23:08:46 PST
[Win] fast/dom/SelectorAPI/resig-SelectorsAPI-test.xhtml is timing out after WebKitRequirements v2024.02.05 History: https://results.webkit.org/?suite=layout-tests&test=fast%2Fdom%2FSelectorAPI%2Fresig-SelectorsAPI-test.xhtml First failure: Buildbot: builder WinCairo-64-bit-Release-Tests build 3448 : 274123@main https://build.webkit.org/#/builders/728/builds/3448 Part of failure diff: https://build.webkit.org/results/WinCairo-64-bit-Release-Tests/274123@main%20(3448)/fast/dom/SelectorAPI/resig-SelectorsAPI-test-diff.txt --- C:\BW\WinCairo-64-bit-Release-Tests\build\layout-test-results\fast/dom/SelectorAPI/resig-SelectorsAPI-test-expected.txt +++ C:\BW\WinCairo-64-bit-Release-Tests\build\layout-test-results\fast/dom/SelectorAPI/resig-SelectorsAPI-test-actual.txt @@ -1,2171 +1,10 @@ +CONSOLE MESSAGE: TypeError: null is not an object (evaluating 'test[1].match(/: ([^\s;]+)/)[1]') +FAIL: Timed out waiting for notifyDone to be called + Selectors API Test Suite WebKitRequirements v2024.02.05 https://github.com/WebKitForWindows/WebKitRequirements/releases/tag/v2024.02.05
Attachments
Fujii Hironori
Comment 1 2024-02-06 23:51:21 PST
I confirmed copying libcurl.dll from the previous WebKitRequirementsWin64.zip v2023.12.06 works around this problem. WebKitRequirements v2024.02.05 upgraded libcurl from 8.5.0 to 8.6.0.
Fujii Hironori
Comment 2 2024-02-07 00:01:32 PST
Using WebInspector debugger, I observed `test[1]` was " background-color:]]><![CDATA[ lime; }". Checking DOM tree with WebInspector, <![CDATA[ ... ]]> was split up to multiple CDATA sections in style element.
Fujii Hironori
Comment 3 2024-02-07 12:38:51 PST
*** This bug has been marked as a duplicate of bug 124566 ***
Note You need to log in before you can comment on or make changes to this bug.