On 15/07/2025 18:13, Diane Trout wrote:
, but I'm not sure that's necessary given all the pytest
and autopkgtest configuration to rerun flaky tests.
Should I push a new dask.distributed with the scipy fix and see if the
current flaky test handling is sufficient?
No, because this already shows it isn't.
There are 2+ issues here:
- (this: Debian#1106105, RC) several tests randomly fail on ppc64el
- (upstream#8977, no Debian number, a bug but non-RC)
test_serialize_scipy_sparse always fails everywhere
and two existing levels of flaky handling:
- Both autopkgtests try 5 times. This ignores some random failures, but
is not sufficient to reliably pass on ppc64el.
- The explicit autopkgtest, but not the pybuild autopkgtest, is marked
flaky at the debian/tests/control level, which means 'run but ignore'.
Because only the explicit autopkgtest has a scipy dependency, the
test_serialize_scipy_sparse failure is already being ignored.
I agree that this isn't a _good_ way to handle the scipy issue and that
we should apply upstream's fix at *some* point, but it's too far into
the freeze to do that now.
I could get test_nanny to never throw an error in the loop by adding
await asyncio.sleep(0.1) into the function before it started trying to
use the cluster
That's plausibly a better idea, but I haven't tried it.
