pointer-lock/lock-already-locked.html is a flaky failure on BigSur and Monterey. History: https://results.webkit.org/?platform=ios&platform=mac&suite=layout-tests&test=pointer-lock%2Flock-already-locked.html Results: https://build.webkit.org/results/Apple-BigSur-Release-WK1-Tests/r281575%20(4845)/results.html Diff: --- /Volumes/Data/worker/bigsur-release-tests-wk1/build/layout-test-results/pointer-lock/lock-already-locked-expected.txt +++ /Volumes/Data/worker/bigsur-release-tests-wk1/build/layout-test-results/pointer-lock/lock-already-locked-actual.txt @@ -1,3 +1,4 @@ +LRP 2004060.937 4 ( 3) 320x 240 P 29.0/ 29.0 35 - -1/ -1 4.8 0/ 0 1 0/ 0 0 [] Test calling lock when already in a locked state. On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
<rdar://problem/82359654>
Updated test expectations at https://trac.webkit.org/changeset/281592/webkit.
This looks like output we've tried to suppress for webrtc tests is leaking into other tests..
*** This bug has been marked as a duplicate of bug 225525 ***
Right, platform/mac/webrtc/captureCanvas-webrtc-software-encoder.html is run just before pointer-lock/lock-already-locked.html... I guess I can change this one to use Baseline and not HighProfile to remove that logging.