-
Notifications
You must be signed in to change notification settings - Fork 72
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
NoSuchElementException when changing parameters #113
Comments
I also have this problem. |
@iphydf I found this happens when you |
Yes, totally :) the reason is that in the previous run the parameters had different values, and it wants to compare the current run with the previous one(s) as part of the overlap test. I would prefer it to assume there was no previous run if the parameter set is different, instead of crashing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Changing the values in a dimension crashes the regression reporter. It seems to expect all current values to exist in the previous runs. This limits the usefulness of regression testing, since there is no way to modify any parameters ever without losing all the history.
Instead of rejecting any histories without a certain value, it may be better to assume the value doesn't exist (and do no comparison), or assume the value was exactly the same as the new one (making comparison a trivial no-op).
Reproduce by running this benchmark twice, changing the value 1 to 2 the second time:
Results in an exception similar to the following:
The text was updated successfully, but these errors were encountered: