found 1150306 7.0.0-2 tags 1150306 trixie thanks Hello. During an archive rebuild of trixie + trixie-proposed-updates, it looks like this is now happening in trixie as well.
As before, the failure rate is a log higher on single-CPU systems, this is my build history on such systems: Status: successful python-psutil_7.0.0-2_amd64-20260913T014939.128Z Status: failed python-psutil_7.0.0-2_amd64-20261119T012513.106Z Status: failed python-psutil_7.0.0-2_amd64-20261119T082254.135Z Status: failed python-psutil_7.0.0-2_amd64-20261119T082313.943Z Status: failed python-psutil_7.0.0-2_amd64-20261119T082313.737Z Status: failed python-psutil_7.0.0-2_amd64-20261119T082314.522Z Status: failed python-psutil_7.0.0-2_amd64-20261119T082315.755Z Status: failed python-psutil_7.0.0-2_amd64-20261119T082357.901Z Status: failed python-psutil_7.0.0-2_amd64-20261119T082404.379Z Status: failed python-psutil_7.0.0-2_amd64-20261119T082418.587Z Status: failed python-psutil_7.0.0-2_amd64-20261119T082423.295Z Status: failed python-psutil_7.0.0-2_amd64-20261119T082424.371Z The package did not change at all, so I guess this can be due to a new glibc or a new kernel, which makes the flaky test to be more flaky. [ I know it's too late to fix this for the next point release this weekend, but maybe for the one after that? I would be willing to help if required ]. Thanks.

