-
Notifications
You must be signed in to change notification settings - Fork 77
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
Don't display invalid results #406
Don't display invalid results #406
Conversation
should we display a message to the user, explaining what happened and that the details view might have useful information? |
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). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have a strong opinion about the exact behavior but this looks reasonable to me. Thanks!
@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 WebKit#399 by not display non-finite scores which are caused by 0-measured suite results. - For non-positive or non-finite scores, the following summary page is displayed. Note that the detailed page is still accessible since you might find some useful information there. - Additionally, a console.error is generated for each zero-sum suite
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