http/tests/inspector/network/resource-timing.html and http/tests/inspector/network/x-frame-options.html have become flaky failures --- /Volumes/Data/slave/mojave-release-tests-wk1/build/layout-test-results/http/tests/inspector/network/resource-timing-expected.txt +++ /Volumes/Data/slave/mojave-release-tests-wk1/build/layout-test-results/http/tests/inspector/network/resource-timing-actual.txt @@ -19,6 +19,7 @@ PASS: responseEnd should come after responseStart. -- Running test case: Resource.TimingData.Redirect +ERROR: Missing frame for given frameId PASS: Start time should be before redirect start time. PASS: Redirect start time should be before redirect end time. PASS: Redirect duration should be at least a few milliseconds. --- /Volumes/Data/slave/mojave-release-tests-wk1/build/layout-test-results/http/tests/inspector/network/x-frame-options-expected.txt +++ /Volumes/Data/slave/mojave-release-tests-wk1/build/layout-test-results/http/tests/inspector/network/x-frame-options-actual.txt @@ -7,5 +7,6 @@ PASS: X-Frame-Options headers should match. -- Running test case: Network.XFrameOptions.Sameorigin +ERROR: Missing frame for given frameId PASS: X-Frame-Options headers should match. https://results.webkit.org/?suite=layout-tests&suite=layout-tests&test=http%2Ftests%2Finspector%2Fnetwork%2Fresource-timing.html&test=http%2Ftests%2Finspector%2Fnetwork%2Fx-frame-options.html
The first failure appears to be at https://trac.webkit.org/changeset/269439/webkit, which was a build fix for: Store WeakPtr<Frame> instead of Frame* https://bugs.webkit.org/show_bug.cgi?id=218599 Seems like that could be related given the error messages in the test being about frames.
<rdar://problem/71646591>
*** This bug has been marked as a duplicate of bug 218830 ***
oops, thanks.