Hello,
What do you think of this "solution" for the freeze for
dask.distributed.
There's a section of get-test-exclusions which skips timing sensitive
tests on riscv64 and s390x.
What I did was add ppc64el to the list of skipped architectures and
said this downgrades the severity of 1106105
I built the patch off the last released commit
2d80190478162a51c5a343e544bf74f500061efc
Avoiding the currently unreleased changes to make it easier to evaluate
this change
Diane
diff --git a/debian/changelog b/debian/changelog
index 2ed4bc0..3cbd925 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+dask.distributed (2024.12.1+ds-2) unstable; urgency=medium
+
+ * Skip timing sensitive tests on ppc64el
+ - distributed has some difficulties launching workers on this
+ architecture, downgrades severity of bug #1106105
+
+ -- Diane Trout <di...@ghic.org> Sun, 20 Jul 2025 20:28:34 -0700
+
dask.distributed (2024.12.1+ds-1) unstable; urgency=medium
* Team upload.
diff --git a/debian/get-test-exclusions b/debian/get-test-exclusions
index 1ab8ee8..21f0247 100755
--- a/debian/get-test-exclusions
+++ b/debian/get-test-exclusions
@@ -104,7 +104,7 @@ esac
# surprizingly s390x. Issue is reproducible while running CPU emulation,
# which may also be an indicator of something else wrong.
case $arch in
- riscv64|s390x)
+ riscv64|s390x|ppc64el)
EXCLUDES+=(
tests/test_asyncprocess.py::test_exit_callback
tests/test_asyncprocess.py::test_num_fds
