control: reassign -1 check On 2022-11-06 17:21, Aurelien Jarno wrote: > On 2022-11-06 08:12, Paul Gevers wrote: > > Source: utox > > Version: 0.18.1-1 > > Severity: serious > > User: debian...@lists.debian.org > > Usertags: regression > > > > Dear maintainer(s), > > > > Your package has an autopkgtest, great. With a recent upload of glibc it > > started to fail on s390x. Looking at the history [1], I noticed that > > apparently the test can flip from passing for a while to failing for a while > > and back. Unfortunately, we don't keep the logs so long to inspect if > > previous (pre August 2022) failures were due to the same reason. > > Unfortunately, the output of the failure is rather limited (it seems there > > is more info logged, but that log file is not echoed to the autopkgtest log > > or stored as an autopkgtest artifact. > > > > Can you please investigate the situation? At least this is a autopkgtest > > regression on a release architecture, but maybe (hopefully?) this points at > > more severe issues. > > > > If you find out that it's really a regression in glibc functionality and the > > upload doesn't "just" trigger faulty behavior in utox, don't hesitate to > > reassign to glibc. Also, don't hesitate to contact the s390x porters if you > > need help figuring out this s390x specific issue. > > For the record, this is the contect of the log file: > > 2/2 Testing: test_chrono > 2/2 Test: test_chrono > Command: "/home/aurel32/utox-0.18.1/build/tests/test_chrono" > Directory: /home/aurel32/utox-0.18.1/build/tests > "test_chrono" start time: Nov 06 10:53 UTC > Output: > ---------------------------------------------------------- > Running suite(s): Chrono > > ================================================================= > ==778737==ERROR: LeakSanitizer: detected memory leaks > > Direct leak of 24 byte(s) in 1 object(s) allocated from: > #0 0x3ffa94b9173 in __interceptor_malloc > ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:69 > #1 0x2aa138068cd in emalloc > (/home/aurel32/utox-0.18.1/build/tests/test_chrono+0x68cd) >
It happens that emalloc is provided by libcheck_pic.a (from the check package) and that ASAN trips when linked objects are built with different GCC versions. In that case both glibc and check needs to be built with the same GCC version. The switch of glibc from GCC 11 to GCC 12 triggered the issue. I am not sure why it happens on s390x only though. It appears that the easiest way to fix the problem is to binNMU check: wb nmu check . ANY . -m 'Rebuild against GCC 12 (Closes: #1023531).' I'll add a breaks on the glibc side once done. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
signature.asc
Description: PGP signature
