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

test_does_not_crash_on_any_valid_code raises hypothesis.errors.FailedHealthCheck in 3.9 #147

Closed
cooperlees opened this issue Nov 23, 2020 · 2 comments · Fixed by #148
Closed

Comments

@cooperlees
Copy link
Collaborator

https://github.com/PyCQA/flake8-bugbear/runs/1444838647
tl;dr

hypothesis.errors.FailedHealthCheck: Data generation is extremely slow: Only produced 7 valid examples in 1.02 seconds (2 invalid ones and 2 exceeded maximum size). Try decreasing size of the data you're generating (with e.g.max_size or max_leaves parameters).
See https://hypothesis.readthedocs.io/en/latest/healthchecks.html for more information about this. If you want to disable just this health check, add HealthCheck.too_slow to the suppress_health_check settings for this test.
@cooperlees cooperlees changed the title test_does_not_crash_on_any_valid_code raises hypothesis.errors.FailedHealthCheck in 3.9 test_does_not_crash_on_any_valid_code raises hypothesis.errors.FailedHealthCheck in 3.9 Nov 23, 2020
@cooperlees
Copy link
Collaborator Author

@Zac-HD - Would love some suggestions here.

I reran the test just to see if it would repro again. It failed on 3.7 this time. Due to this happening on different runtimes, should I add the too_slow and move on or do you think there is a found regression here?

I will try and find how I pass this with the @given decorator.

@Zac-HD
Copy link
Member

Zac-HD commented Nov 23, 2020

I'd probably just add too_slow and move on - this is probably due to VM contention or something rather than a change in the code.

cooperlees added a commit that referenced this issue Nov 23, 2020
- We sometimes get to slow
- This is probably due to VM resources

Fixes #147
cooperlees added a commit that referenced this issue Nov 23, 2020
- We sometimes get to slow
- This is probably due to VM resources

Fixes #147
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants