Source: twisted
Version: 25.5.0-2
Severity: serious
User: [email protected]
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed that it regularly fails. I copied some of the log below, the error message suggests to disable the health check for ci systems like autopkgtest.

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/t/twisted/testing/amd64/64613189/

275s hypothesis.errors.FailedHealthCheck: Input generation is slow: Hypothesis only generated 2 valid inputs after 2.42 seconds.
275s
275s                count | fraction |    slowest draws (seconds)
275s operations | 2 | 100% | -- -- -- -- 2.417
275s
275s This could be for a few reasons:
275s 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(). 275s 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.
275s
275s 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.
275s
275s twisted.internet.test.test_abstract.WriteBufferingTests.test_writeBuffering

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to