Source: ocrmypdf Version: 16.10.4+dfsg1-1 Severity: serious User: [email protected] Usertags: flaky
Dear maintainer(s),I looked at the results of the autopkgtest of your package because it showed up as regression for pytest and node-jquery. I noticed that it regularly fails. An example can be found below. Please be aware that most hosts running tests for ci.d.n are running multiple tests in parallel, so item 2 of the message is expected to apply.
Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Don't hesitate to reach out if you need help and some more information from our infrastructure. Paul https://ci.debian.net/packages/o/ocrmypdf/testing/amd64/64343099/394s =================================== FAILURES =================================== 394s _____________________ test_calculate_downsample_hypothesis _____________________
394s
394s @given(
394s > st.one_of(st.just("RGB"), st.just('L')),
394s ^^^
394s st.integers(min_value=1, max_value=100000),
394s st.integers(min_value=1, max_value=100000),
394s st.integers(min_value=64, max_value=100000),
394s st.integers(min_value=64, max_value=100000),
394s st.integers(min_value=64 * 64, max_value=1000000),
394s )
394s E hypothesis.errors.FailedHealthCheck: Input generation is slow:
Hypothesis only generated 2 valid inputs after 2.46 seconds.
394s E 394s E count | fraction | slowest draws (seconds)394s E max_bytes | 2 | 100% | -- -- -- -- 2.455 394s E mode | 2 | 0% | -- -- -- -- -- 394s E im_h | 2 | 0% | -- -- -- -- -- 394s E max_x | 2 | 0% | -- -- -- -- -- 394s E im_w | 2 | 0% | -- -- -- -- -- 394s E max_y | 2 | 0% | -- -- -- -- --
394s E 394s E This could be for a few reasons:394s E 1. This strategy could be generating too much data per input. Try decreasing the amount of data generated, for example by decreasing the minimum size of collection strategies like st.lists(). 394s E 2. Some other expensive computation could be running during input generation. For example, if @st.composite or st.data() is interspersed with an expensive computation, HealthCheck.too_slow is likely to trigger. If this computation is unrelated to input generation, move it elsewhere. Otherwise, try making it more efficient, or disable this health check if that is not possible.
394s E394s E If you expect input generation to take this long, you can disable this health check with @settings(suppress_health_check=[HealthCheck.too_slow]). See https://hypothesis.readthedocs.io/en/latest/reference/api.html#hypothesis.HealthCheck for details.
394s 394s tests/test_imageops.py:34: FailedHealthCheck
OpenPGP_signature.asc
Description: OpenPGP digital signature
