RESOLVED WONTFIX172092
[macOS Debug WK1] fast/parser/adoption-agency-unload-iframe-4.html is a flaky timeout (always on iOS 10 Release WK1)
https://bugs.webkit.org/show_bug.cgi?id=172092
Summary [macOS Debug WK1] fast/parser/adoption-agency-unload-iframe-4.html is a flaky...
David Kilzer (:ddkilzer)
Reported 2017-05-14 03:56:55 PDT
LayoutTests/fast/parser/adoption-agency-unload-iframe-4.html is: - a flaky timeout on macOS Debug WK1 - always times out on iOS 10 Release WK1. This test was added for: Bug 168458: REGRESSION(r212218): Assertion failures in and after parserRemoveChild https://bugs.webkit.org/show_bug.cgi?id=168458 https://trac.webkit.org/r212621
Attachments
David Kilzer (:ddkilzer)
Comment 1 2017-05-14 04:06:00 PDT
Same test always times out on GTK port: Bug 169211: REGRESSION(r213446): [GTK] Layout test fast/parser/adoption-agency-unload-iframe-4.html timeouts https://bugs.webkit.org/show_bug.cgi?id=169211
David Kilzer (:ddkilzer)
Comment 2 2017-05-14 04:09:05 PDT
(In reply to David Kilzer (:ddkilzer) from comment #1) > Same test always times out on GTK port: > > Bug 169211: REGRESSION(r213446): [GTK] Layout test > fast/parser/adoption-agency-unload-iframe-4.html timeouts > https://bugs.webkit.org/show_bug.cgi?id=169211 Furthermore, analysis in Bug 169211 says the GTK test timeouts were caused by r213446: Bug 169079: Allow render tree building before loading stylesheet elements ​https://bugs.webkit.org/show_bug.cgi?id=169079 https://trac.webkit.org/r213446
David Kilzer (:ddkilzer)
Comment 3 2017-05-14 04:17:31 PDT
Updated TestExpectations: Committed r216842: <https://trac.webkit.org/r216842>
David Kilzer (:ddkilzer)
Comment 4 2017-05-14 04:28:48 PDT
(In reply to David Kilzer (:ddkilzer) from comment #3) > Updated TestExpectations: > > Committed r216842: <https://trac.webkit.org/r216842> And: Committed r216843: <https://trac.webkit.org/r216843>
Jonathan Bedard
Comment 5 2025-12-18 20:54:08 PST
We don't run this configuration any more, and this test does not time out on all the configuration we support.
Note You need to log in before you can comment on or make changes to this bug.