Your message dated Sat, 25 Jul 2026 18:55:42 -0700 with message-id <[email protected]> and subject line dask.distributed: Test failure during build has caused the Debian Bug report #1098228, regarding dask.distributed: Test failure during build to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1098228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098228 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: dask.distributed Version: 2022.12.1+ds.1 Severity: important dask.distributed FTBFS on bookworm with: FAILED ../../../distributed/tests/test_chaos.py::test_KillWorker[segfault] - TimeoutError: Test timeout after 30s. FAILED ../../../distributed/tests/test_worker.py::test_worker_descopes_data - AssertionError: assert not {<weakref at 0x3ffa8e37a10; to 'C' at 0x3ff67f23e50>} -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.12.13-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---Version debian/2024.5.2+ds.1-6 thanks we "solved" it by disabling the test. Even upstream has a lot of trouble with getting networking tests to work reliably.
--- End Message ---
