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
Using Angular 17.3.0 and Wallaby 1.0.292 (JetBrains plugin), we're now getting consistent errors where we weren't getting errors before: Error: Timeout - Async function did not complete within 5000ms.
Tests all run fine with karma/jasmine, but wallaby fails.
We have also checked out a branch from over a week ago, which used to pass 100% but that now fails with the same errors also, so we assume something in Wallaby has changed to cause these errors.
We've reviewed our recent changes for the last month, and could not identify a possible change that would cause your project to stop working.
It looks like your diagnostic report was truncated, so without the log information, we can't troubleshoot much further. If you're concerned about sharing the rest of the report publicly for privacy reasons, you can email it to us directly: hello@wallabyjs.com.
Is it possible that you updated your dependencies and didn't reinstall them when you reverted to a previous branch?
You may also try to downgrade your Wallaby version to confirm that is the cause of your problem. You may do this by following our Offline Installation instructions and using a previous version. If you do find that a previous version is working, can you please let us know which version starts breaking for you?
Wallaby now errors on code that hasn't changed
Using Angular 17.3.0 and Wallaby 1.0.292 (JetBrains plugin), we're now getting consistent errors where we weren't getting errors before: Error: Timeout - Async function did not complete within 5000ms.
Tests all run fine with karma/jasmine, but wallaby fails.
We have also checked out a branch from over a week ago, which used to pass 100% but that now fails with the same errors also, so we assume something in Wallaby has changed to cause these errors.
Wallaby diagnostics report
The text was updated successfully, but these errors were encountered: