I’ve seen something similar before too. I just used the new executable anyway, and it was fine.
To fix it, for starters you’ll need to go into the logs, and find which test actually failed.
I’ve seen something similar before too. I just used the new executable anyway, and it was fine.
To fix it, for starters you’ll need to go into the logs, and find which test actually failed.