#1111610 getrouterinfo autopkgtest regressed on amd64/arm64

#1111610#5
Date:
2025-08-20 01:33:25 UTC
From:
To:
Hi terceiro and elbrus,

After the release of trixie, we have uploaded curl 8.15.0 to unstable
but it's failing to migrate to testing [1] because
prometheus-mysqlrouter-exporter/6.0.0-5 autopkgtests fails with 8.15.0
[2] and passes with 8.14.1 (the one in testing) [3]. Taking a closer
look, I realized the problem is a bit more complicated than a failed
test. The tldr of it is:

The long story is prometheus-mysqlrouter-exporter's autopkgtests were
failing because mysql-server and mysql-router aren't available in
testing. Elbrus filled a bug for that (#1108802) and it was fixed by
adding "skip-not-installable restriction to getrouterinfo to prevent
break in testing and stable where mysql-server and mysql-router are
unavailable".

That's fine, the autopkgtest fails, but succeeds :-) and we move on. The
problem happens when the regression testing kicks in to check if adding
only curl from unstable breaks prometheus-mysqlrouter-exporter's
autopkgtests. In doing that, unstable is added and curl is pinned to
unstable, that's also fine and expected. But somehow (maybe we need to
set unstable's preference to -1?) mysql-router and mysql-router are also
picked from the unstable feed [4]. So basically we have the reference and
the regression testing doing two extremely different things.

Only for amd64, the exporter does not seems to be ready in the 60
seconds sleep and doesn't return data so the test fails. Since it passed
on all other arches, we don't think is a curl problem, but I'm reporting
it because of the conceptual problem in the previous paragraph.

Cheers,
Charles

[1] https://qa.debian.org/excuses.php?package=curl
[2] https://ci.debian.net/packages/p/prometheus-mysqlrouter-exporter/testing/amd64/63463584/
[3] https://ci.debian.net/packages/p/prometheus-mysqlrouter-exporter/testing/amd64/63463585/
[4] https://ci.debian.net/packages/p/prometheus-mysqlrouter-exporter/testing/amd64/63463584/#L135

#1111610#10
Date:
2025-08-20 05:50:35 UTC
From:
To:
Hi,

[Leaving all original text for prometheus-mysqlrouter-exporter maintainers]


If infrastructure related, it's bin:autopkgtest and not src:debci.


That's indeed a consequence of using skip-not-installable.


and arm64 in unstable (often?) too.


I regret that I ever invented skip-not-installable, because the current
situation is one result of it.

Paul

#1111610#23
Date:
2025-08-29 15:43:48 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
prometheus-mysqlrouter-exporter, 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 1111610@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lena Voytek <lena.voytek@canonical.com> (supplier of updated prometheus-mysqlrouter-exporter 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 ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Fri, 29 Aug 2025 10:24:38 -0400
Source: prometheus-mysqlrouter-exporter
Built-For-Profiles: noudeb
Architecture: source
Version: 6.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
Changed-By: Lena Voytek <lena.voytek@canonical.com>
Closes: 1111610
Changes:
 prometheus-mysqlrouter-exporter (6.0.1-1) unstable; urgency=medium
 .
   * New upstream version 6.0.1.
   * d/rules: modernize and sync with other exporters' style.
     - Standardize executable name as prometheus-mysqlrouter-exporter.
     - Generate manpage from --help-man.
   * d/docs: Ship upstream README with package.
   * d/manpages: Ship generated manpage with package.
   * d/gitlab-ci.yml, d/.gitignore: Update gitlab-ci.yml to latest template.
   * d/control: Refresh to match latest dh-make-golang template.
     - Move source package to section: golang.
     - Swap from Built-Using to Static-Build-Using.
   * d/service: Add systemd service for faster setup.
   * d/default: Add default file for using env vars and args with service.
   * d/README.Debian: Provide setup instructions for running the service.
   * d/tests: Update tests to match new binary name and service.
   * d/t/control: Set getrouterinfo test to flaky instead to avoid
     inconsistencies between stable and unstable. (Closes: #1111610)
Checksums-Sha1:
 3414cb3ee4b435bfad5f6e7beb0df86a7fe3f7f5 2480 prometheus-mysqlrouter-exporter_6.0.1-1.dsc
 60731f6e8bec59cae59a70c317624631881abe51 316528 prometheus-mysqlrouter-exporter_6.0.1.orig.tar.gz
 bf5bb5bb23c0fc4c7fd9f09915217951e96eb4e3 5408 prometheus-mysqlrouter-exporter_6.0.1-1.debian.tar.xz
 94d4ac0f3d3370219be31ffdc102848981d82fab 9479 prometheus-mysqlrouter-exporter_6.0.1-1_source.buildinfo
Checksums-Sha256:
 522ae4e2d50986d2987994777d109b1f9bb9940bcd43c064e4203145c974d506 2480 prometheus-mysqlrouter-exporter_6.0.1-1.dsc
 33a41bd3a71105124c995b75b1cb761e62ff15e3ee7a387a7d1136905591adae 316528 prometheus-mysqlrouter-exporter_6.0.1.orig.tar.gz
 91a86055ebfa8349a9c9aff087f4f4d22dea005691d88852b14bf7a74843ea09 5408 prometheus-mysqlrouter-exporter_6.0.1-1.debian.tar.xz
 a5af55df827908ff67864111124309e223058a3a41617c2d2e2d46e394729acc 9479 prometheus-mysqlrouter-exporter_6.0.1-1_source.buildinfo
Files:
 db970b885ad8cc06b98854588055fd36 2480 golang optional prometheus-mysqlrouter-exporter_6.0.1-1.dsc
 ddc5632dcd0bd17605e79f3ba876146c 316528 golang optional prometheus-mysqlrouter-exporter_6.0.1.orig.tar.gz
 0429ede2cd1f0199120146e22af64296 5408 golang optional prometheus-mysqlrouter-exporter_6.0.1-1.debian.tar.xz
 35bd4ba046b9f5e342c963ba78b8850b 9479 golang optional prometheus-mysqlrouter-exporter_6.0.1-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEY+78PeFNUUbOfyS/NLitfZUp55MFAmixuNQACgkQNLitfZUp
55MMCA/+LFKNHPcmj3OeG23yMpr+kXxyooZX8l07e/wFNx+nWgf+mJEN51RntPGT
kV1JYNYBgN8F2VovxbXVPpDP9HDIhY4lQN599+joftRnPJ1hlxiwvipQjdwl7kNr
GjSDE1Ry4P1uUTVDNU9+QY2yZl5iGUfM3OxJ5gTOUsxUzoHd+EGf53syPZJC49Ub
C+cX1m2Axx8nzwaBNP/Q40LD8s0FffYRe8b04Bvw5Lpr3+tgZdnZQzjIQsHhtVWy
EMsB7+JIgQoStr2sxHTNY1y2u4YZMf2C7QUIs9MzqIMrhhVV/ZGEPyBHN9D0h45v
xu1MJ4TJJUy4Eb0lH043iBAo3d6BiNX7XJTwTgP2iclyxu/qmiEYVE4coqDRMyD2
1gFGj7h/Ux1xHiSvRh3oVIbP9Ji6757ka6RVn6+Zkp7fc9dZO8J0rjZipwcX4Rdp
ZZ3rWfqQ2+NzRAQsgkuPbyyKg5hZOjvknX6DqRDQpdtAptwOACBFreaRc7yAMcyD
Ru5I1qxiMqY+xyzlQ6uY8FV0U8CN0UPB569AKuGIVjf1HVyiFfmQKK4I0P38DH1o
yFEs6vYEuFd6azp45cBPgmRXAgY2vRt2vv6hPHwF0kQVUHKlsUs5LiMaJ0IPYpub
0Wx2Cuis4HBDJQtvoPR+hDhGhUZu0jcnp/lSm4uihPuan+cqRDk=
=+QpZ
-----END PGP SIGNATURE-----

#1111610#26
Date:
2025-08-29 15:44:57 UTC
From:
To:
Hello,

Bug #1111610 in prometheus-mysqlrouter-exporter reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/go-team/packages/prometheus-mysqlrouter-exporter/-/commit/adac46828b25b52e0d50cec992831434c3086b6c
------------------------------------------------------------------------
Set getrouterinfo test to flaky instead to avoid inconsistencies between
stable and unstable.
(Closes: #1111610)
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1111610

#1111610#33
Date:
2025-08-30 00:33:55 UTC
From:
To:
Hi Paul,

Sorry for the late response.

Ack.

So, shouldn't we pin the unstable as -1 and only pin the package that
triggered the regression testing to 900, in order to always make sure
nothing else come from unstable? I think I might be missing some
implications of this behaviour, right? Anyway, thanks for reassigning. I
saw it was fixed today.

Oh, well, we all regret something... But you can always remove it in a
future major release ;-)

Cheers,
Charles

#1111610#38
Date:
2025-08-30 05:49:20 UTC
From:
To:
Hi,


No, because then the fallback wouldn't work and we'd get much more
problems. autopkgtest already has an option to be stricter, but that
caused more issues than it solved when I used that for some time on the
ci.d.n infrastructure.


No, I tried. It was deliberately decided that what we now have is the
less bad option.


True. I don't regret it enough yet to go through that effort, but maybe
others will.

Paul