Your message dated Fri, 07 Nov 2025 19:35:37 +0000
with message-id <[email protected]>
and subject line Bug#1120170: fixed in bbmap 39.20+dfsg-3
has caused the Debian Bug report #1120170,
regarding bbmap autopkgtest uses insane amount of memory
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.)
--
1120170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120170
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: bbmap
Version: 39.20+dfsg-2
Severity: important
User: [email protected]
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of your package because I was
investigating memory issues on our ci.d.n infrastructure. I noticed that
your package uses an insane amount of memory.
On our amd64 worker, I saw it peaking at 51% of 250 GB. On our loong64
worker I saw it peaking at 83% of 127 GB. Now there's an argument to
make that the infra should protect itself against this kind of
misbehavior, but currently it doesn't (we're working on that). I would
appreciate it if you limit the test on memory usage.
In the past I already added a reject list entry on riscv64 as the test
times out. It also seems to take much more time on loong64 than on other
architectures, so I'm also going to add it to the reject list for
loong64 too. You don't need to investigate this as riscv64 has some
under powered workers so I consider that an infrastructure problem and
loong64 isn't a release architecture yet, but solutions for both
architectures are welcome.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: bbmap
Source-Version: 39.20+dfsg-3
Done: Étienne Mollier <[email protected]>
We believe that the bug you reported is fixed in the latest version of
bbmap, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Étienne Mollier <[email protected]> (supplier of updated bbmap package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 07 Nov 2025 19:51:46 +0100
Source: bbmap
Architecture: source
Version: 39.20+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
<[email protected]>
Changed-By: Étienne Mollier <[email protected]>
Closes: 1120170
Changes:
bbmap (39.20+dfsg-3) unstable; urgency=medium
.
* autopkgtest-memory.patch: new: cap memory during autopkgtest.
The memory cap should not affect regular user workloads. This change
is brought to avoid hogging autopkgtest runners. (Closes: #1120170)
* d/control: drop redundant Rules-Requires-Root: no.
* d/watch: convert to v5 SourceForge redirector.
Checksums-Sha1:
cbbb8d979a53d176c447935f7e52ec55c6a4036c 2286 bbmap_39.20+dfsg-3.dsc
7811c81729942a034b115307a9ee5b180916bede 27024 bbmap_39.20+dfsg-3.debian.tar.xz
Checksums-Sha256:
1fcb6dae155d116ddb29c86162e0b48e3d6aba35b28c0b26f3ea9204e1f1d7bd 2286
bbmap_39.20+dfsg-3.dsc
ed7b8d96da4a4bf1e98a0b3ee0132e4adde0e6d40c661ee22d697ff4a34dc06d 27024
bbmap_39.20+dfsg-3.debian.tar.xz
Files:
1ad9849a60eb8d83e15092c38593d470 2286 science optional bbmap_39.20+dfsg-3.dsc
b231def873f6c1bd52b640df71847c1d 27024 science optional
bbmap_39.20+dfsg-3.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmkOQTIUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdqp7A/9GFVXVMEboBayEyODons/SI/zdsZj
7AMlvdXruhcwsO9euBizdlz6S6AGQpEmavfJIKYH/6zsGtfABpNlyYIfboJefB63
chj0l0V8AwSnXoU//gCJYDuXglag5KwVlz9WiuFupAaahvuQwaTEHKI4xzz0ngv+
8ikLGnuADTlKk1wJbmSfSqxRLT4xgexosI+bzInuAr2XTuacb5R3jZPHJTsGw2Q7
YEljoPWSZqqeD6Whe7v3kY2VoTpxEAH4NkSzygpmwCdL80x6KLn0kVIveIBokOsi
uhchY1rxa3a+1Ya/ncBQFAJdvxsCWi5TQA6BKlmXHfSxOa7WRPZNOX80KB5rwQaH
ZDX7I25roEVJVbTNmkQizUHStKSUV3uqALSZ7RNnK2gOgxYDcseLIWYqS/jWTIYX
Zdo53k3Rx4JAul5U9TenSmuMxVwCVlIchbUyVKKsaxLX2qVoqAc+pLB8UL9wnuV4
a6kYR4XLrWImTtp5gEqpKqWalPiygjohqyJz3JhshQxwnWHiy6CciF8TaQic2DxN
6lLFL1vVeomA2kFA9Z8YaeRV8YNUQnQsTD5eYfCfJAQQjFbfdzf4vUVCVoaBWaud
6P/Fveh/EHcMSOCvU/hVKr4HsmVuDK1pC6ESj/oEmvSp1nUcf5xsBqyMWThE1l9t
lK0moQX0kW8mNuU=
=nifA
-----END PGP SIGNATURE-----
pgpE39EY7FPFr.pgp
Description: PGP signature
--- End Message ---
