Description: fast/animation/request-animation-frame-throttling-detached-iframe.html The test was consistently passing. Ventura release wk1 began fail in range https://commits.webkit.org/compare/264776@main...264774@main . Ventura release wk2 arm64 began to fail in range https://commits.webkit.org/compare/259505@main...259498@main . Monterey release wk1 x86_64 began to fail in range https://commits.webkit.org/compare/264914@main...264911@main . On the bots that the test is failing it is a constant failure. On the bots that it is passing it is constantly passing. This issue can be reproduced on bot212 using the command: run-webkit-tests --no-build --release --dump-render-tree --debug-rwt-logging --no-retry-failures fast/animation/request-animation-frame-throttling-detached-iframe.html History: https://results.webkit.org/?limit=5000&suite=layout-tests&test=fast%2Fanimation%2Frequest-animation-frame-throttling-detached-iframe.html&platform=mac&style=release&recent=false Diff: @@ -4,27 +4,27 @@ PASS internals.requestAnimationFrameThrottlingReasons() is "[Unthrottled]" -PASS internals.requestAnimationFrameInterval is 0.015 +FAIL internals.requestAnimationFrameInterval should be 0.015. Was 0.03333333333333333. PASS frame.contentWindow.internals.requestAnimationFrameThrottlingReasons() is "[Unthrottled]" -PASS frame.contentWindow.internals.requestAnimationFrameInterval is 0.015 +FAIL frame.contentWindow.internals.requestAnimationFrameInterval should be 0.015. Was 0.03333333333333333. internals.setLowPowerModeEnabled(true); PASS internals.requestAnimationFrameThrottlingReasons() is "LowPowerMode" -PASS internals.requestAnimationFrameInterval is 0.030 +FAIL internals.requestAnimationFrameInterval should be 0.03. Was 0.06666666666666667. PASS frame.contentWindow.internals.requestAnimationFrameThrottlingReasons() is "LowPowerMode" -PASS frame.contentWindow.internals.requestAnimationFrameInterval is 0.030 +FAIL frame.contentWindow.internals.requestAnimationFrameInterval should be 0.03. Was 0.06666666666666667. frame.remove() document.body.appendChild(frame) PASS internals.requestAnimationFrameThrottlingReasons() is "LowPowerMode" -PASS internals.requestAnimationFrameInterval is 0.030 +FAIL internals.requestAnimationFrameInterval should be 0.03. Was 0.06666666666666667. PASS frame.contentWindow.internals.requestAnimationFrameThrottlingReasons() is "LowPowerMode" -PASS frame.contentWindow.internals.requestAnimationFrameInterval is 0.030 +FAIL frame.contentWindow.internals.requestAnimationFrameInterval should be 0.03. Was 0.06666666666666667. frame.remove() internals.setLowPowerModeEnabled(false); PASS internals.requestAnimationFrameThrottlingReasons() is "[Unthrottled]" -PASS internals.requestAnimationFrameInterval is 0.015 +FAIL internals.requestAnimationFrameInterval should be 0.015. Was 0.03333333333333333. document.body.appendChild(frame) PASS frame.contentWindow.internals.requestAnimationFrameThrottlingReasons() is "[Unthrottled]" -PASS frame.contentWindow.internals.requestAnimationFrameInterval is 0.015 +FAIL frame.contentWindow.internals.requestAnimationFrameInterval should be 0.015. Was 0.03333333333333333. PASS successfullyParsed is true TEST COMPLETE
<rdar://problem/115154068>
Test gardening commit 267768@main (de704f24e0ca): <https://commits.webkit.org/267768@main> Reviewed commits have been landed. Closing PR #17575 and removing active labels.
This is a failure in WK1, and in WK2 only on Ventura E wk2 Release on Macmini9,1 with arm64. Is there a chance that bot is mis-configured with a non-60Hz refresh rate?
Refresh rate is indeed set to 75 Hz on bot156. I changed it to 60Hz. Let's have this bug track the WebKit1 failure.
Typo, it was bot256.
The test is failing on Sonoma Debug wk1 and wk2.
Test gardening commit 269716@main (8e5d7efef25c): <https://commits.webkit.org/269716@main> Reviewed commits have been landed. Closing PR #19486 and removing active labels.
bot688 - The refresh rate is set to 75 Hz, I changed it to 60Hz.
bot687 - The refresh rate is set to 75 Hz, I changed it to 60Hz
bot674 - The refresh rate is set to 75 Hz, I changed it to 60Hz
Confirmed that after changing refresh rate from 75 Hz to 60 Hz on Sonoma bots, the test began passing consistently on Sonoma.