Hi Ferenc,
On 2026-10-22 09:33, Ferenc Wágner wrote:
Credential passing over UNIX sockets is core functionality of libqb.
Skipping the libqb build time (and autopkg-) tests would certainly be
possible, but I'm worried that the built library would trigger the same
OOPS running the tests of the entire HA stack above it (kronosnet,
corosync, pacemaker, and so on). The current libqb package (2.0.9-1+b1)
apparently did not fail the latest corosync build for example, but like
above, I don't understand why and thus I don't know what to expect from
disabling the tests.
Can you perhaps provide some additional insight here?
I don't think I have additional insight. Except that I'm wondering if
it's worth holding back the update of libqb for this kernel issue on an
architecture we haven't release with yet. Do you think this could be a
mis-compilation that we would slip into testing? I was expecting/hoping
this is a kernel issue, so it might affect the version of libqb in
testing already if the kernel it runs on is affected. Also Aurelien
showed he can trigger the issue on all architectures, but apparently
only testsuites on loong64 trigger it in the wild.
I just ran the autopkgtest in testing on ci.d.n manually, it passes. I
also run an autopkgtest from an unpacked source version 2.0.10-1, which
means that autopkgtest builds the binaries and runs the autopkgtests.
They pass. Build time tests are skipped by autopkgtest builds though.
loongson@ci-worker-loong64-01:~$ uname -a
Linux ci-worker-loong64-01 7.2.11+deb14-loong64 #1 SMP PREEMPT Debian
7.2.11-1 (2026-10-15) loongarch64 GNU/Linux
Paul
