dask.distributed has both an explicit autopkgtest that is marked as
flaky, and a pybuild-autopkgtest that isn't, that run mostly the same
tests. (The git log says this is to have both a needs-internet and a
non-needs-internet test, but the set of tests also differs because they
have different Depends. In particular, the test_serialize_scipy_sparse
failures
(https://github.com/dask/distributed/commit/94222c0fc49c3ad14353611ecdc2c699b97bf8d4)
are *not* part of this bug because that is only run by the
marked-as-flaky test.) Both of them *already* try 5 times (see
debian/run-tests).
The debci logs seem to have two kinds of pybuild-autopkgtest failure:
- Scheduler.computations contains multiple entries (the exact number
varies) where only one is expected. Can occur in
tests/test_client.py::test_computation_object_code_client_submit_list_comp,
tests/test_client.py::test_computation_object_code_client_submit_dict_comp,
and/or tests/test_computations.py::test_computations_futures.
e.g.
https://ci.debian.net/packages/d/dask.distributed/testing/ppc64el/60904054/
- Timeout in tests/test_tls_functional.py::test_retire_workers.
e.g.
https://ci.debian.net/packages/d/dask.distributed/testing/ppc64el/60794087/
This package already has a mechanism for excluding tests on some
architectures (debian/get-test-exclusions), so we could skip these tests
on ppc64el, but I don't yet know if we want to.
