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
I noticed that #14055 if failing only on the prod and jquery suite. I dug further and it would appear that engines + visit + shouldRender: true causes some issues with the run loop in the tests, but only in prod and jquery extended prototype suites.
Should not be in a run loop at end of test Ember run should not have scheduled timers at end of test Assertion Failed: You have turned on testing mode, which disabled the run-loop's autorun. You will need to wrap any code with asynchronous side-effects in a run
Thanks @rwjblue. This issue was happening both before and after that PR.
I've confirmed locally that this issue happens when enableoptionalfeatures is both on and off, which would suggest that the issue is independent of glimmer.
I noticed that #14055 if failing only on the prod and jquery suite. I dug further and it would appear that engines +
visit
+shouldRender: true
causes some issues with the run loop in the tests, but only in prod and jquery extended prototype suites.Should not be in a run loop at end of test
Ember run should not have scheduled timers at end of test
Assertion Failed: You have turned on testing mode, which disabled the run-loop's autorun. You will need to wrap any code with asynchronous side-effects in a run
Here is a failing PR to repro: #14085
cc @dgeb @krisselden @trentmwillis
The text was updated successfully, but these errors were encountered: