You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some strategy, elements are manually pushed on the stack. But it can already be 1024 element and raise a StackOverflowError.
By trying to raise the error (by trying to generate a stack with 1024, hypothesis raise a FailedHealthCheck
@given(evm=arithmetic_tests_strategy)
> def test_add(self, cairo_run, evm: Evm):
E hypothesis.errors.FailedHealthCheck: The smallest natural example for your test is extremely large. This makes it difficult for Hypothesis to generate good examples, especially when trying to reduce failing ones at the end. Consider reducing the size of your data if it is of a fixed size. You could also fix this by improving how your data shrinks (see https://hypothesis.readthedocs.io/en/latest/data.html#shrinking for details), or by introducing default values inside your strategy. e.g. could you replace some arguments with their defaults by using one_of(none(), some_complex_strategy)?
E 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.large_base_example to the suppress_health_check settings for this test.
It seems then that the case of a stack with 1024 is never generated by hypothesis
The text was updated successfully, but these errors were encountered:
Hola. I'm Tobias and I'm new to the space. I've already contributed to some projects and would like to add this to my pool of experience plus I recently learned rust and cairo
In some strategy, elements are manually pushed on the stack. But it can already be 1024 element and raise a StackOverflowError.
By trying to raise the error (by trying to generate a stack with 1024, hypothesis raise a FailedHealthCheck
It seems then that the case of a stack with 1024 is never generated by hypothesis
The text was updated successfully, but these errors were encountered: