Your message dated Tue, 26 Jul 2022 10:25:51 +0200
with message-id <82b8da9d-5249-96cf-44b9-bcb49259b...@debian.org>
and subject line Re: balboa: regression + flaky autopkgtest: regularly times
out on amd64, i386 and s390x
has caused the Debian Bug report #1013938,
regarding balboa: regression + flaky autopkgtest: regularly times out on amd64,
i386 and s390x
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 ow...@bugs.debian.org
immediately.)
--
1013938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: balboa
Version: 2.0.0+ds-4
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of you package because it was
showing up on our "slow" page [1]. I noticed that there were several
runs that took 2:47 (our timeout time), while successful runs more in
the order of minutes. This started to happen recently.
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.
On top of that, when a test just hangs that's not good for our
infrastructure. I'll put balboa on our reject_list for amd64, i386, and
s390x.
Don't hesitate to reach out if you need help and some more information
from our infrastructure.
Paul
[1] https://ci.debian.net/status/slow/
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi Paul,
[...]
On top of that, when a test just hangs that's not good for our
infrastructure. I'll put balboa on our reject_list for amd64, i386,
and s390x.
I see. I wonder what the procedure to get off that list is?
Normally closing this bug. :) However, for testing to get fixed, we need
rocksdb to migrate (which is currently stalled due to binutils and
gcc-12 issues). Let's assume that will happen some time.
This migration has happened in the meantime [0] and autopkgtests for
balboa now succeed again within <1 minute [1]. I guess we can close this
now.
If there are still objections please feel free to reply and reopen.
Cheers
Sascha
[0]
https://tracker.debian.org/news/1345579/rocksdb-722-5-migrated-to-testing/
[1] https://ci.debian.net/packages/b/balboa/testing/amd64/
--- End Message ---
