-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with restarting tests and runaway node processes #3165
Comments
I'm also frequently seeing a problem where the pass/fail counts are not reset between runs, but accumulate over multiple runs. Unfortunately I'm not sure the minimal repo shows this problem, so I'm hoping it's related. |
We'd appreciate you sharing this with us. If you have a github repo, you can add me to it and I can take a look. Alternatively, you may email the repo to hello@wallabyjs.com. |
Thanks for the sample repo. We identified a bug affected more recent versions of Wallaby with Vitest where Wallaby's cancellation token wasn't being correctly processed between test runs. This has been fixed in Wallaby core This definitely fixes the We also couldn't reproduce the empty |
I went back and looked at the issues that I've submitted over the last 6 months or so, and out of 5 or 6 debug reports all but one had the debug array empty. I would say it happens pretty much all the time right now. Is there a way I can test it. I'm thinking if I just do 'Copy diagnostics report' with no error then it would be empty anyway? |
The tests not restarting issue seems to be solved, and so far I've not seen any runaway node processes, so thanks very much for the fix. I am however still seeing issues with the pass/fail counts. It's a bit hit and miss to get it to repeat, but if I repeatedly type/delete |
I can reproduce the test count issue. Will let you know when we have a fix. |
We've found a problem for some configurations when a test run has been scheduled but and not started, and then another test run is scheduled. This can happy when errors fail very fast (e.g. such as syntax errors with We have fixed the problem in Wallaby core |
I love how all I need to do is get a reliable repro and you guys have squashed the bug dead before I wake up the next morning : ) Thanks! So this just leaves the empty debug array, which I don't think you've been able to reproduce. That's not a burning issue for me right now. Close this issue? |
The empty debug array is still a little strange, but I think we can go ahead and close this issue. Thanks again for the repo to reproduce the problem, it does really help us. |
This is happening again for me. Repo: https://github.com/tslocke/wallaby-issue-2023.11 It's non-deterministic so it can take a few goes to see the problem. If you open the test file and repeatedly delete and retype some parts of I'm also seeing non-terminating node processes at 100% CPU, which I presume is connected. |
Thanks for the sample repo. There was a bug processing tests when using Please update to Wallaby core |
I should note, in this case, I believe that the node processes may continue to live because Wallaby never cleaned them up. If you're still seeing runaway node processes, please let us know. |
Working great now. Now sign of runaway process. Thanks! |
BTW I did see the |
If it persists, could you please let us know. Maybe it was just a one off. |
Two things that seem like they might be related.
Wallaby seems to sometimes have trouble restarting the test run. I most often see this if I'm isolating or skipping a test (.only / .skip). I start typing the .skip, Wallaby starts running and then gets stuck on e.g.
TypeError: test.sk is not a function
I am also very often seeing multiple node processes stuck at 100%, which I have to kill manually.
And one other thing - as you can see below, the diagnostics report has the empty debug array, which you have mentioned previously as something that should not happen. I bring it up again because I finally made a stripped down repo that I can share if you need it (but not publicly). It shows all of these problems.
Thanks
The text was updated successfully, but these errors were encountered: