219225 2020-11-20 14:30:57 -0800 REGRESSION (r269359): [ Mac ] http/tests/inspector/dom/disconnect-dom-tree-after-main-frame-navigation.html is flaky failing 2020-12-07 15:49:59 -0800 1 1 1 Unclassified WebKit Web Inspector WebKit Nightly Build Unspecified Unspecified NEW InRadar P2 Normal --- 1 tsavell webkit-unassigned hi inspector-bugzilla-changes webkit-bot-watchers-bugzilla webkit-bug-importer oldest_to_newest 1709654 0 tsavell 2020-11-20 14:30:57 -0800 http/tests/inspector/dom/disconnect-dom-tree-after-main-frame-navigation.html This test began failing around r269439. I am able to reproduce this currently but cannot bisect the issue. History: https://results.webkit.org/?suite=layout-tests&test=http%2Ftests%2Finspector%2Fdom%2Fdisconnect-dom-tree-after-main-frame-navigation.html Diff: --- /Volumes/Data/slave/catalina-release-tests-wk2/build/layout-test-results/http/tests/inspector/dom/disconnect-dom-tree-after-main-frame-navigation-expected.txt +++ /Volumes/Data/slave/catalina-release-tests-wk2/build/layout-test-results/http/tests/inspector/dom/disconnect-dom-tree-after-main-frame-navigation-actual.txt @@ -1,6 +1,7 @@ Testing that DOMTrees are not retained by DOMTreeManager across main frame navigations. +ERROR: Missing frame for given frameId == Running test suite: DOM.DisconnectTreeOnMainResourceChange -- Running test case: CheckLazyInitializationOfDOMTree Reproduced with command: run-webkit-tests --iterations 2000 --exit-after-n-failures 1 --exit-after-n-crashes-or-timeouts 1 --debug-rwt-logging --no-retry --force --no-build -f http/tests/inspector/dom/disconnect-dom-tree-after-main-frame-navigation.html 1709655 1 webkit-bug-importer 2020-11-20 14:31:18 -0800 <rdar://problem/71642438> 1709659 2 tsavell 2020-11-20 14:37:56 -0800 This test was last modified in r269359. likely regression point then 1712646 3 tsavell 2020-12-07 15:49:59 -0800 Marked this as failing in https://trac.webkit.org/changeset/270527/webkit