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
Although this is not a critical issue, I'd suggest to have a look into it when we have time to improve the product.
If Jest tests fails by timeout, the following warning is displayed: A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them. Steps to reproduce:
maybe we should at least mention it in the documentation? of for instance pass jest timeout to the threshold if it's present by default?
The problem is also that we leave lots of scans, which either get disrupted or running forever (like the LFI one, I have scans running 2+ days old, although usually it takes minutes to finish).
Although this is not a critical issue, I'd suggest to have a look into it when we have time to improve the product.
If Jest tests fails by timeout, the following warning is displayed:
A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them.
Steps to reproduce:
Relates to #74
The text was updated successfully, but these errors were encountered: