Your message dated Mon, 03 Aug 2026 21:24:03 -0700
with message-id <[email protected]>
and subject line Re: dask.distributed: flaky autopkgtest on ppc64el
has caused the Debian Bug report #1106105,
regarding dask.distributed: flaky autopkgtest on ppc64el
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.)


-- 
1106105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106105
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: dask.distributed
Version: 2024.12.1+ds-1
Severity: serious
User: [email protected]
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package because it showed up in the migration excuses for python-tornado on ppc64el. Because I was suspecting flaky behavior, I scheduled 5 runs of the test. 3/5 failed. The history shows occasional failure. I'm slightly suspecting the failures depend on the load of the host, I do see spikes in memory usage (which my be filesystem usages because of tmpfs) and number of threads while the 5 tests were running (in parallel).

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Version 2024.12.1+ds-3
thanks

Debian CI has had a chance to run the autopkgtests and everything but
armel passed, and armel is tagged n/a tmpfail.

I think we've got it.

Diane

--- End Message ---

Reply via email to