Your message dated Thu, 23 May 2024 20:50:07 +0000
with message-id <e1safo3-0051kh...@fasolo.debian.org>
and subject line Bug#1067705: fixed in siridb-server 2.0.51-3
has caused the Debian Bug report #1067705,
regarding src:siridb-server: flaky autopkgtest: curl: (7) Failed to connect to
localhost port 9020 after 0 ms: Couldn't connect to server
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.)
--
1067705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: siridb-server
Version: 2.0.51-2
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of your package. I noticed
that it regularly fails. From a distance, this looks like a race
condition. Should the test ensure the server is started?
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
[1] https://ci.debian.net/packages/s/siridb-server/testing/amd64/44324499/
19s autopkgtest [11:10:05]: test http-api: [-----------------------
19s * fixing /etc/siridb/siridb.conf
19s * restarting siridb-server
19s * run queries
19s get-version
19s curl: (7) Failed to connect to localhost port 9020 after 0 ms:
Couldn't connect to server
19s cat: res.txt: No such file or directory
19s autopkgtest [11:10:05]: test http-api: -----------------------]
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: siridb-server
Source-Version: 2.0.51-3
Done: Paul Gevers <elb...@debian.org>
We believe that the bug you reported is fixed in the latest version of
siridb-server, 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 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Paul Gevers <elb...@debian.org> (supplier of updated siridb-server 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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Thu, 23 May 2024 22:34:09 +0200
Source: siridb-server
Architecture: source
Version: 2.0.51-3
Distribution: unstable
Urgency: medium
Maintainer: SiriDB Maintainers
<team+debian-siridb-packaging-t...@tracker.debian.org>
Changed-By: Paul Gevers <elb...@debian.org>
Closes: 1067705
Changes:
siridb-server (2.0.51-3) unstable; urgency=medium
.
* tests: add --retry to first curl to avoid failing if siridb-server
isn't ready yet (Closes: #1067705)
Checksums-Sha1:
28b15a02ad189e8331a620f439f8a224e141d454 2002 siridb-server_2.0.51-3.dsc
69a1e1ab269448a02056fbfc984cef696aaa64c9 5680
siridb-server_2.0.51-3.debian.tar.xz
Checksums-Sha256:
950b0cebaf51a6fff37a058c49a6e1ad4695e7d5a7c15dfc61b76056225ada22 2002
siridb-server_2.0.51-3.dsc
01d2854a1962e9c20ca5e8a541784e1f69c3641ca66ac5c75e18510f74bb3947 5680
siridb-server_2.0.51-3.debian.tar.xz
Files:
88ba64c03939a2311b0d7a46b657d995 2002 database optional
siridb-server_2.0.51-3.dsc
708f720f190ed6fe6a7ec20db08d5d5c 5680 database optional
siridb-server_2.0.51-3.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmZPqJEACgkQnFyZ6wW9
dQrkowgAiB9gOK3jeL+UTMxpBAVlybJp1eWnM4rGbrhP8zaJaIXXQz18TmmWIpd0
M6fsup3lucU5DUK4u8wc5z/QUfqExAVDkrzDBmR/VVNnYC3TD0hP/dNIlbLxIHHo
PPk9J/nu2SbchhlcTFuStpS60nLvr0jmcgeHoO1750Jm+fnEvOJcGlqBuoKu7iy9
1wKPtNh3Om4ODKPIlSV6gBhs6WoTqJ/EeO7n6RlBsvJczHUIJwdSmqiphz7SWmCl
jkoZ3dxaOLbuDLJqbSd5ppOGkpwGaRc/OMx3nmv9dsi8JBzO9q8Z1IUZT3IsojSt
V8o4CNw78EOcgyr3nn+r4Jxsc/5W6Q==
=4djY
-----END PGP SIGNATURE-----
pgp25pW6AJLUT.pgp
Description: PGP signature
--- End Message ---
