Closed camillobruni closed 1 month ago
should we display a message to the user, explaining what happened and that the details view might have useful information?
Updated version with a better description:
Rather than "Invalid Score", how about "Error"? Also, we should probably stop right away when we detect an invalid value instead of running 'til completion.
Updated the code to stop after the first iteration with a broken score (tracking errors across the TestInvoker seems a bit more tricky at the moment).
@rniwa could you have another look maybe?
@rniwa do you have additional feedback or would be ok with landing with your proposed changes?
This partially fixes #399 by not display non-finite scores which are caused by 0-measured suite results.
console.error
is generated for each zero-sum suite