You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the last few months, one single test on the Windows CI test job has been failing, making the whole build red:
Chrome Headless 120.0.6099.225 (Windows 10) Util #requestAnimFrame calles a function on next frame, unless canceled FAILED
Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
I can't for the life of me figure out why it doesn't run the supplied function. I think the only thing that changed is Windows image version — from 20231029.1.0 to 20231115.2.0. Also weird that just that test is failing. One thing I tried is testing whether the native window.requestAnimationFrame works fine in the test (in place of Util.requestAnimFrame), and it weirdly does. Not sure what else to try. Any ideas? cc @jonkoops
The text was updated successfully, but these errors were encountered:
For the last few months, one single test on the Windows CI test job has been failing, making the whole build red:
I can't for the life of me figure out why it doesn't run the supplied function. I think the only thing that changed is Windows image version — from 20231029.1.0 to 20231115.2.0. Also weird that just that test is failing. One thing I tried is testing whether the native
window.requestAnimationFrame
works fine in the test (in place ofUtil.requestAnimFrame
), and it weirdly does. Not sure what else to try. Any ideas? cc @jonkoopsThe text was updated successfully, but these errors were encountered: