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 use pitest on a big project. It take a lot of time, so I've this stack :
Info : Created 93 mutation test units
Warning: Minion exited abnormally due to TIMED_OUT
Warning: Minion exited abnormally due to TIMED_OUT
Warning: Minion exited abnormally due to TIMED_OUT
Warning: Minion exited abnormally due to TIMED_OUT
I understand the utility of the Warning, but often someone-else think the build is KO and stop-it.
can I have some log like
33/93 mutations test units remaining
between the warnings? It will be more user-friendly
The text was updated successfully, but these errors were encountered:
The complete message includes the time where it's been executed. You could use this as reference to see if the build is KO. It can't help you that much about what is left to be done.
It's not exactly the same case, but #516 proposes to add some logs regarding the number of mutations remaining to test (it logs every 100 test however, and that might not be often enough if you have a lot of timeouts and... less than 100 tests).
I use pitest on a big project. It take a lot of time, so I've this stack :
I understand the utility of the Warning, but often someone-else think the build is KO and stop-it.
can I have some log like
between the warnings? It will be more user-friendly
The text was updated successfully, but these errors were encountered: