Skip to content
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

Be smarter about Overrun #18

Open
Seelengrab opened this issue Feb 27, 2024 · 0 comments
Open

Be smarter about Overrun #18

Seelengrab opened this issue Feb 27, 2024 · 0 comments
Labels
errors Related to error messages UX Issues relating to UX

Comments

@Seelengrab
Copy link
Owner

Currently, Overrun is simply caught and marked as a regular rejection, but it would be better to report to the user that an Overrun occurred. This way, a user is informed that their exploration exhausts the maximum number of choices per TestCase and that they should consider either increasing the memory limit through the configuration, or limit their maximum sizes so the choices taken in their particular implementation don't hit the overrun limits anymore.

@Seelengrab Seelengrab added errors Related to error messages feature This is related to a new feature labels Feb 27, 2024
@Seelengrab Seelengrab changed the title Don't catch Overrun Be smarter about Overrun Mar 2, 2024
@Seelengrab Seelengrab added UX Issues relating to UX and removed feature This is related to a new feature labels Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
errors Related to error messages UX Issues relating to UX
Projects
None yet
Development

No branches or pull requests

1 participant