I agree that xfailing the tests *may* be a reasonable solution. I'm
only saying that it should be done by someone with more idea than me of
whether these particular tests are important, because blindly xfailing
everything that fails is effectively not having tests.
If we do choose that approach, at least test_balance_expensive_tasks
needs to be an outright xfail/skip not just a flaky, because when it
fails it fails repeatedly.
On 06/02/2023 19:38, Diane Trout wrote:
The most important thing about dask / dask.distributed is they really
should be at about the same upstream version.
I knew that, and was planning on 2022.12.1 of both when I decided to go
ahead with pandas. What went wrong was that I only tested a build, not
an autopkgtest, and thought the failing tests were dask.distributed's
(known) inability to run all its tests in a buildd environment.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027254#21
I'm not 100% sure how to
mark that in the d/control file.
Possibly
Depends: python3-dask (>= 2022.12.1~), python3-dask (<< 2022.12.2~)
but I haven't tested that.
