Your message dated Sat, 17 Sep 2022 11:38:42 +0200
with message-id <yywvonlatl5t2...@msg.df7cb.de>
and subject line Re: Bug#1019121: libpqtypes: flaky autopkgtest on arm64: table
"libpq_array" does not exist
has caused the Debian Bug report #1019121,
regarding libpqtypes: flaky autopkgtest on arm64: table "libpq_array" does not
exist
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.)
--
1019121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpqtypes
Version: 1.5.1-7
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 on arm64.
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
Ran 125 tests - 1 failed
*** /tmp/pg_virtualenv.QzsWeE/log/postgresql-14-regress.log (last 100
lines) ***
2022-09-02 13:57:21.320 CST [7664] LOG: starting PostgreSQL 14.5
(Debian 14.5-1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian
12.1.0-8) 12.1.0, 64-bit
2022-09-02 13:57:21.321 CST [7664] LOG: listening on IPv6 address
"::1", port 5433
2022-09-02 13:57:21.321 CST [7664] LOG: listening on IPv4 address
"127.0.0.1", port 5433
2022-09-02 13:57:21.321 CST [7664] LOG: listening on Unix socket
"/tmp/.s.PGSQL.5433"
2022-09-02 13:57:21.322 CST [7665] LOG: database system was shut down
at 2022-09-02 13:57:21 CST
2022-09-02 13:57:21.327 CST [7664] LOG: database system is ready to
accept connections
2022-09-02 13:57:23.522 CST [7685] debci@postgres ERROR: table
"libpq_array" does not exist
2022-09-02 13:57:23.522 CST [7685] debci@postgres STATEMENT: DROP TABLE
libpq_array
2022-09-02 13:57:23.525 CST [7685] debci@postgres ERROR: type
"public.complex" does not exist
2022-09-02 13:57:23.525 CST [7685] debci@postgres STATEMENT: DROP TYPE
public.complex
2022-09-02 13:57:23.525 CST [7685] debci@postgres ERROR: type
"public.simple" does not exist
2022-09-02 13:57:23.525 CST [7685] debci@postgres STATEMENT: DROP TYPE
public.simple
https://ci.debian.net/data/autopkgtest/testing/arm64/libp/libpqtypes/25613424/log.gz
https://ci.debian.net/data/autopkgtest/testing/arm64/libp/libpqtypes/24974038/log.gz
https://ci.debian.net/data/autopkgtest/testing/arm64/libp/libpqtypes/24648942/log.gz
https://ci.debian.net/data/autopkgtest/testing/arm64/libp/libpqtypes/24021115/log.gz
https://ci.debian.net/data/autopkgtest/testing/arm64/libp/libpqtypes/23016446/log.gz
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 1.5.1-8
Re: Paul Gevers
> I looked at the results of the autopkgtest of your package. I noticed that
> it regularly fails on arm64.
Hi Paul,
I think I found the problem - it's not flaky, but it was failing when
the system timezone wasn't UTC. Some of the arm64 workers are set to
CDT.
The tests are pinned to run with UTC now, and
https://ci.debian.net/packages/libp/libpqtypes/testing/arm64/
seems happy.
Thanks for the report,
Christoph
--- End Message ---
