gcc-mozilla_6.4.0-0+deb8u1_amd64.changes REJECTED
No target suite found. Please check your target distribution and that you uploaded to the right archive. Mapping oldoldstable-security to oldoldstable-proposed-updates. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.
Processed: Re: Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)
Processing commands for cont...@bugs.debian.org: > reassign 935902 g++-9 Bug #935902 [libcppunit-dev] libcppunit-dev: segfault when using with a program compiled with g++-9 Bug reassigned from package 'libcppunit-dev' to 'g++-9'. No longer marked as found in versions cppunit/1.14.0-4. Ignoring request to alter fixed versions of bug #935902 to the same values previously set > affects 935902 libcppunit-dev Bug #935902 [g++-9] libcppunit-dev: segfault when using with a program compiled with g++-9 Added indication that 935902 affects libcppunit-dev > found 935902 9.2.1-12 Bug #935902 [g++-9] libcppunit-dev: segfault when using with a program compiled with g++-9 Marked as found in versions gcc-9/9.2.1-12. > close 935902 9.2.1-16 Bug #935902 [g++-9] libcppunit-dev: segfault when using with a program compiled with g++-9 Marked as fixed in versions gcc-9/9.2.1-16. Bug #935902 [g++-9] libcppunit-dev: segfault when using with a program compiled with g++-9 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 935902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)
reassign 935902 g++-9 affects 935902 libcppunit-dev found 935902 9.2.1-12 close 935902 9.2.1-16 thanks Hi, On Thu, Oct 31, 2019 at 03:15:10PM +0100, Matthias Klose wrote: > The comment about cppunit made me look at the cppunit package to find > #935902, and yes, the test case is reproducible. So looking at the test Ah, that one... Reassigning to gcc (and marking as fixed) > failure would have been revealed that the test frame work is broken, not a > single test. This turned out to be https://gcc.gnu.org/PR92267, causing an > ABI breakage in cppunit. OK. > The fix is now in -16. Good. Can confirm. You can close the bug. Regards, Rene
Results for 9.2.1 20191030 (Debian 9.2.1-16) testsuite on s390x-ibm-linux-gnu
LAST_UPDATED: Wed Oct 30 12:04:51 UTC 2019 (revision 277619) === acats tests === === acats Summary === # of expected passes2320 # of unexpected failures0 Native configuration is s390x-ibm-linux-gnu === g++ tests === Running target unix FAIL: c-c++-common/asan/global-overflow-1.c -O2 output pattern test FAIL: c-c++-common/asan/global-overflow-1.c -O3 -g output pattern test FAIL: c-c++-common/asan/global-overflow-1.c -Os output pattern test FAIL: c-c++-common/asan/global-overflow-1.c -O2 -flto -fno-use-linker-plugin -flto-partition=none output pattern test FAIL: c-c++-common/asan/global-overflow-1.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects output pattern test FAIL: g++.dg/asan/function-argument-3.C -O0 execution test FAIL: g++.dg/asan/function-argument-3.C -O1 output pattern test FAIL: g++.dg/asan/function-argument-3.C -O2 output pattern test FAIL: g++.dg/asan/function-argument-3.C -O3 -g output pattern test FAIL: g++.dg/asan/function-argument-3.C -Os output pattern test FAIL: g++.dg/asan/function-argument-3.C -O2 -flto -fno-use-linker-plugin -flto-partition=none output pattern test FAIL: g++.dg/asan/function-argument-3.C -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects output pattern test FAIL: g++.dg/asan/large-func-test-1.C -O2 output pattern test FAIL: g++.dg/asan/large-func-test-1.C -O3 -g output pattern test FAIL: g++.dg/asan/large-func-test-1.C -Os output pattern test FAIL: g++.dg/asan/large-func-test-1.C -O2 -flto -fno-use-linker-plugin -flto-partition=none output pattern test FAIL: g++.dg/asan/large-func-test-1.C -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects output pattern test FAIL: c-c++-common/Wattributes.c -std=gnu++98 (test for errors, line 404) FAIL: c-c++-common/Wattributes.c -std=gnu++14 (test for errors, line 404) FAIL: c-c++-common/Wattributes.c -std=gnu++17 (test for errors, line 404) FAIL: g++.dg/gomp/tls-5.C -std=c++14 scan-assembler-not .data FAIL: g++.dg/gomp/tls-5.C -std=c++17 scan-assembler-not .data FAIL: g++.dg/guality/pr55665.C -O2 line 23 p == 40 FAIL: g++.dg/guality/pr55665.C -O3 -g line 23 p == 40 FAIL: g++.dg/guality/pr55665.C -O2 -flto -fno-use-linker-plugin -flto-partition=none line 23 p == 40 FAIL: g++.dg/tls/thread_local7.C -std=c++14 scan-assembler-not .data FAIL: g++.dg/tls/thread_local7.C -std=c++17 scan-assembler-not .data FAIL: g++.dg/tls/thread_local7g.C -std=c++14 scan-assembler-not .data FAIL: g++.dg/tls/thread_local7g.C -std=c++17 scan-assembler-not .data === g++ Summary for unix === # of expected passes133012 # of unexpected failures29 # of expected failures 524 # of unsupported tests 6501 Running target unix/-fstack-protector FAIL: c-c++-common/asan/global-overflow-1.c -O2 output pattern test FAIL: c-c++-common/asan/global-overflow-1.c -O3 -g output pattern test FAIL: c-c++-common/asan/global-overflow-1.c -Os output pattern test FAIL: c-c++-common/asan/global-overflow-1.c -O2 -flto -fno-use-linker-plugin -flto-partition=none output pattern test FAIL: c-c++-common/asan/global-overflow-1.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects output pattern test FAIL: g++.dg/asan/function-argument-3.C -O0 execution test FAIL: g++.dg/asan/function-argument-3.C -O1 output pattern test FAIL: g++.dg/asan/function-argument-3.C -O2 output pattern test FAIL: g++.dg/asan/function-argument-3.C -O3 -g output pattern test FAIL: g++.dg/asan/function-argument-3.C -Os output pattern test FAIL: g++.dg/asan/function-argument-3.C -O2 -flto -fno-use-linker-plugin -flto-partition=none output pattern test FAIL: g++.dg/asan/function-argument-3.C -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects output pattern test FAIL: g++.dg/asan/large-func-test-1.C -O2 output pattern test FAIL: g++.dg/asan/large-func-test-1.C -O3 -g output pattern test FAIL: g++.dg/asan/large-func-test-1.C -Os output pattern test FAIL: g++.dg/asan/large-func-test-1.C -O2 -flto -fno-use-linker-plugin -flto-partition=none output pattern test FAIL: g++.dg/asan/large-func-test-1.C -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects output pattern test FAIL: c-c++-common/Wattributes.c -std=gnu++98 (test for errors, line 404) FAIL: c-c++-common/Wattributes.c -std=gnu++14 (test for errors, line 404) FAIL: c-c++-common/Wattributes.c -std=gnu++17 (test for errors, line 404) FAIL: g++.dg/gomp/tls-5.C -std=c++14 scan-assembler-not .data FAIL: g++.dg/gomp/tls-5.C -std=c++17 scan-assembler-not .data FAIL: g++.dg/guality/pr55665.C -O2 line 23 p == 40 FAIL: g++.dg/guality/pr55665.C -O3 -g line 23 p == 40 FAIL: g++.dg/guality/pr55665.C -O2 -flto -fno-use-linker-plugin -flto-partition=none line 23 p == 40 FAIL: g++.dg/tls/thread_local7.C -std=c++14 scan-assembler-not .data FAIL:
Results for 9.2.1 20191030 (Debian 9.2.1-16) testsuite on i686-pc-linux-gnu
LAST_UPDATED: Wed Oct 30 12:04:51 UTC 2019 (revision 277619) === acats tests === === acats Summary === # of expected passes2320 # of unexpected failures0 Native configuration is i686-pc-linux-gnu === brig tests === Running target unix === brig Summary === # of unsupported tests 1 === g++ tests === Running target unix FAIL: g++.dg/abi/anon1.C -std=c++98 scan-assembler-not globl FAIL: g++.dg/abi/anon1.C -std=c++14 scan-assembler-not globl FAIL: g++.dg/abi/anon1.C -std=c++17 scan-assembler-not globl FAIL: g++.dg/abi/anon4.C -std=c++98 scan-assembler-not comdat FAIL: g++.dg/abi/anon4.C -std=c++14 scan-assembler-not comdat FAIL: g++.dg/abi/anon4.C -std=c++17 scan-assembler-not comdat FAIL: g++.dg/pr71694.C -std=gnu++98 scan-assembler-not movl FAIL: g++.dg/pr71694.C -std=gnu++14 scan-assembler-not movl FAIL: g++.dg/pr71694.C -std=gnu++17 scan-assembler-not movl FAIL: g++.dg/pr80481.C -std=gnu++98 scan-assembler-not vmovaps FAIL: g++.dg/pr80481.C -std=gnu++14 scan-assembler-not vmovaps FAIL: g++.dg/pr80481.C -std=gnu++17 scan-assembler-not vmovaps FAIL: g++.dg/stackprotectexplicit2.C -std=gnu++98 scan-assembler-times stack_chk_fail 2 FAIL: g++.dg/stackprotectexplicit2.C -std=gnu++14 scan-assembler-times stack_chk_fail 2 FAIL: g++.dg/stackprotectexplicit2.C -std=gnu++17 scan-assembler-times stack_chk_fail 2 FAIL: g++.dg/guality/pr55665.C -O2 line 23 p == 40 FAIL: g++.dg/guality/pr55665.C -O3 -g line 23 p == 40 FAIL: g++.dg/guality/pr55665.C -O2 -flto -fno-use-linker-plugin -flto-partition=none line 23 p == 40 FAIL: g++.dg/ubsan/vla-1.C -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test === g++ Summary for unix === # of expected passes133263 # of unexpected failures19 # of expected failures 524 # of unsupported tests 5891 Running target unix/-fstack-protector FAIL: g++.dg/abi/anon1.C -std=c++98 scan-assembler-not globl FAIL: g++.dg/abi/anon1.C -std=c++14 scan-assembler-not globl FAIL: g++.dg/abi/anon1.C -std=c++17 scan-assembler-not globl FAIL: g++.dg/abi/anon4.C -std=c++98 scan-assembler-not comdat FAIL: g++.dg/abi/anon4.C -std=c++14 scan-assembler-not comdat FAIL: g++.dg/abi/anon4.C -std=c++17 scan-assembler-not comdat FAIL: g++.dg/pr71694.C -std=gnu++98 scan-assembler-not movl FAIL: g++.dg/pr71694.C -std=gnu++14 scan-assembler-not movl FAIL: g++.dg/pr71694.C -std=gnu++17 scan-assembler-not movl FAIL: g++.dg/pr80481.C -std=gnu++98 scan-assembler-not vmovaps FAIL: g++.dg/pr80481.C -std=gnu++14 scan-assembler-not vmovaps FAIL: g++.dg/pr80481.C -std=gnu++17 scan-assembler-not vmovaps FAIL: g++.dg/stackprotectexplicit2.C -std=gnu++98 scan-assembler-times stack_chk_fail 2 FAIL: g++.dg/stackprotectexplicit2.C -std=gnu++14 scan-assembler-times stack_chk_fail 2 FAIL: g++.dg/stackprotectexplicit2.C -std=gnu++17 scan-assembler-times stack_chk_fail 2 FAIL: g++.dg/guality/pr55665.C -O2 line 23 p == 40 FAIL: g++.dg/guality/pr55665.C -O3 -g line 23 p == 40 FAIL: g++.dg/guality/pr55665.C -O2 -flto -fno-use-linker-plugin -flto-partition=none line 23 p == 40 FAIL: g++.dg/ubsan/vla-1.C -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test === g++ Summary for unix/-fstack-protector === # of expected passes133263 # of unexpected failures19 # of expected failures 524 # of unsupported tests 5891 === g++ Summary === # of expected passes266526 # of unexpected failures38 # of expected failures 1048 # of unsupported tests 11782 /build/gcc-9-fnrkiF/gcc-9-9.2.1/build/gcc/xg++ version 9.2.1 20191030 (Debian 9.2.1-16) === gcc tests === Running target unix FAIL: gcc.dg/sibcall-11.c scan-assembler jmp FAIL: gcc.dg/graphite/interchange-1.c scan-tree-dump graphite "tiled" FAIL: gcc.dg/graphite/interchange-10.c scan-tree-dump graphite "tiled" FAIL: gcc.dg/graphite/interchange-11.c scan-tree-dump graphite "tiled" FAIL: gcc.dg/graphite/interchange-3.c scan-tree-dump graphite "tiled" FAIL: gcc.dg/graphite/interchange-4.c scan-tree-dump graphite "tiled" FAIL: gcc.dg/graphite/interchange-7.c scan-tree-dump graphite "tiled" FAIL: gcc.dg/graphite/interchange-9.c scan-tree-dump graphite "tiled" FAIL: gcc.dg/graphite/uns-interchange-9.c scan-tree-dump graphite "tiled" XPASS: gcc.dg/guality/example.c -O0 execution test XPASS: gcc.dg/guality/example.c -O1 -DPREVENT_OPTIMIZATION execution test XPASS: gcc.dg/guality/example.c -O2 -DPREVENT_OPTIMIZATION execution test XPASS: gcc.dg/guality/example.c -Og -DPREVENT_OPTIMIZATION execution test XPASS: gcc.dg/guality/example.c -O2 -flto -fno-use-linker-plugin -flto-partition=none -DPREVENT_OPTIMIZATION execution test XPASS: gcc.dg/guality/guality.c -O0 execution test XPASS:
Results for 9.2.1 20191030 (Debian 9.2.1-16) testsuite on arm-unknown-linux-gnueabi
LAST_UPDATED: Wed Oct 30 12:04:51 UTC 2019 (revision 277619) Native configuration is arm-unknown-linux-gnueabi === libatomic tests === Running target unix === libatomic Summary === # of expected passes44 # of unsupported tests 5 === libffi tests === Running target unix === libffi Summary === # of expected passes2214 === libgo tests === Running target unix FAIL: os FAIL: runtime FAIL: sync/atomic === libgo Summary === # of expected passes181 # of unexpected failures3 /build/gcc-9-rxWBY5/gcc-9-9.2.1/build/./gcc/gccgo version 9.2.1 20191030 (Debian 9.2.1-16) === libgomp tests === Running target unix === libgomp Summary === # of expected passes6357 # of expected failures 4 # of unsupported tests 422 === libphobos tests === Running target unix FAIL: libphobos.phobos/std/math.d execution test WARNING: libphobos.phobos/std/range/package.d (test for excess errors) program timed out. FAIL: libphobos.phobos/std/range/package.d (test for excess errors) UNRESOLVED: libphobos.phobos/std/range/package.d compilation failed to produce executable FAIL: libphobos.phobos/std/zip.d execution test FAIL: libphobos.phobos_shared/std/math.d execution test WARNING: libphobos.phobos_shared/std/range/package.d (test for excess errors) program timed out. FAIL: libphobos.phobos_shared/std/range/package.d (test for excess errors) UNRESOLVED: libphobos.phobos_shared/std/range/package.d compilation failed to produce executable FAIL: libphobos.phobos_shared/std/zip.d execution test === libphobos Summary === # of expected passes744 # of unexpected failures6 # of unresolved testcases 2 # of unsupported tests 2 === libstdc++ tests === Running target unix FAIL: 22_locale/time_get/get_time/char/2.cc execution test FAIL: 22_locale/time_get/get_time/char/wrapped_env.cc execution test FAIL: 22_locale/time_get/get_time/char/wrapped_locale.cc execution test FAIL: 22_locale/time_get/get_time/wchar_t/2.cc execution test FAIL: 22_locale/time_get/get_time/wchar_t/wrapped_env.cc execution test FAIL: 22_locale/time_get/get_time/wchar_t/wrapped_locale.cc execution test FAIL: libstdc++-prettyprinters/80276.cc whatis p4 FAIL: libstdc++-prettyprinters/80276.cc whatis p4 === libstdc++ Summary === # of expected passes13462 # of unexpected failures8 # of expected failures 78 # of unsupported tests 371 === acats tests === === acats Summary === # of expected passes2320 # of unexpected failures0 === g++ tests === Running target unix FAIL: g++.dg/other/anon5.C -std=gnu++98 (test for excess errors) FAIL: g++.dg/other/anon5.C -std=gnu++14 (test for excess errors) FAIL: g++.dg/other/anon5.C -std=gnu++17 (test for excess errors) FAIL: g++.dg/guality/pr55665.C -O2 line 23 p == 40 FAIL: g++.dg/guality/pr55665.C -O3 -g line 23 p == 40 FAIL: g++.dg/guality/pr55665.C -O2 -flto -fno-use-linker-plugin -flto-partition=none line 23 p == 40 FAIL: g++.dg/lto/pr65276 cp_lto_pr65276_0.o-cp_lto_pr65276_1.o link, -flto -O0 -std=c++11 FAIL: g++.dg/vect/pr87914.cc -std=c++98 execution test FAIL: g++.dg/vect/pr87914.cc -std=c++14 execution test FAIL: g++.dg/vect/pr87914.cc -std=c++17 execution test === g++ Summary === # of expected passes130485 # of unexpected failures10 # of expected failures 511 # of unsupported tests 6555 /build/gcc-9-rxWBY5/gcc-9-9.2.1/build/gcc/xg++ version 9.2.1 20191030 (Debian 9.2.1-16) === gcc tests === Running target unix FAIL: gcc.dg/gimplefe-28.c (internal compiler error) FAIL: gcc.dg/gimplefe-28.c (test for excess errors) FAIL: gcc.dg/ira-shrinkwrap-prep-1.c scan-rtl-dump pro_and_epilogue "Performing shrink-wrapping" FAIL: gcc.dg/graphite/interchange-1.c scan-tree-dump graphite "tiled" FAIL: gcc.dg/graphite/interchange-10.c scan-tree-dump graphite "tiled" FAIL: gcc.dg/graphite/interchange-11.c scan-tree-dump graphite "tiled" FAIL: gcc.dg/graphite/interchange-3.c scan-tree-dump graphite "tiled" FAIL: gcc.dg/graphite/interchange-4.c scan-tree-dump graphite "tiled" FAIL: gcc.dg/graphite/interchange-7.c scan-tree-dump graphite "tiled" FAIL: gcc.dg/graphite/interchange-9.c scan-tree-dump graphite "tiled" FAIL: gcc.dg/graphite/uns-interchange-9.c scan-tree-dump graphite "tiled" XPASS: gcc.dg/guality/example.c -O0 execution test XPASS: gcc.dg/guality/example.c -O1 -DPREVENT_OPTIMIZATION execution test XPASS: gcc.dg/guality/example.c -O2 -DPREVENT_OPTIMIZATION execution test XPASS: gcc.dg/guality/example.c -Os -DPREVENT_OPTIMIZATION execution test XPASS: gcc.dg/guality/example.c -Og -DPREVENT_OPTIMIZATION
Re: Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)
>> And afaik there was no test rebuild for bullseye >> either. > > It does not help to blame people for not doing a rebuild when there is no rebuild necessary. Please could you turn off your mode feeling attacked by any email, before you understood these? On 31.10.19 15:33, rene.engelh...@mailbox.org wrote: Hi, Am 31. Oktober 2019 15:15:10 MEZ schrieb Matthias Klose : And afaik there was no test rebuild for bullseye either. Accepted cppunit 1.14.0-4 (source) into unstable On July 26: https://tracker.debian.org/news/1049803/accepted-cppunit-1140-4-source-into-unstable/ Buster release was 3 weeks before that. So this "no test rebuild for bullseye" is not true. bullseye didn't see any test rebuild of the archive, and filing of FTBFS bugs yet.
Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)
Hi, Am 31. Oktober 2019 15:15:10 MEZ schrieb Matthias Klose : >And afaik there was no test rebuild for >bullseye >either. Accepted cppunit 1.14.0-4 (source) into unstable On July 26: https://tracker.debian.org/news/1049803/accepted-cppunit-1140-4-source-into-unstable/ Buster release was 3 weeks before that. So this "no test rebuild for bullseye" is not true. Regards Rene -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)
Hi, Am 31. Oktober 2019 15:15:10 MEZ schrieb Matthias Klose : >On 29.10.19 15:09, Vincent Lefevre wrote: >> On 2019-10-29 13:09:46 +0100, rene.engelh...@mailbox.org wrote: >>> Am 29. Oktober 2019 12:49:44 MEZ schrieb Vincent Lefevre >: In case makefile magic triggers some rebuild, you can also run the generated executable directly (with the right environment >variables, in case this matters). If the programs honors the system ABI, this is allowed, and you'll effectively test the new libstdc++6. >>> >>> No, if the rebuild rebuilds cppunittester or one of the >>> exceptionprotectors or the smoketest so or similar we are at the >>> same situation as with the autopkgtest (that's what it builds) and >>> are not sure whether it's g++-9 or libstdc++6. Neither LO nor the >>> test are an executable it's a executable with gazillions of .sos. >> >> I meant running the generated program (smoketest) without rebuilding >> it: >> >> 1. Build smoketest with the old g++-9 / libstdc++6. >> 2. Upgrade g++-9 / libstdc++6. >> 3. Run smoketest directly. >> >> (I assume that the smoketest executable does not invoke g++-9 to >> rebuild things on the fly.) > >I'm not sure if Rene wants to help tracking this down, he just disabled >running >the test in >https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/99764f8d0df2f40aba9a220a8a4858d3f6d05494 *temporarily* >and introducing a typo in >https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/998c3b1c63bbedf8d886227749279d7ccb26a30b >So maybe don't commit if you are angry. > Maybe, yes, but I needed to get it builds le got the upload. Will fix, thanks. ><_rene_> how supported is clang on the various (release) archs? ><_rene_> completely? ><_rene_> (clang++ if it matters) ><_rene_> (actually probably only matters for amd64/arm64 for now, >but...) > >so I assume we cannot expect Rene's help for that issue anymore. Unfortunately the tests fail when LO is built with clang. So yes, we need to track it down. >The comment about cppunit made me look at the cppunit package to find >#935902, >and yes, the test case is reproducible. So looking at the test failure >would >have been revealed that the test frame work is broken, not a single >test. I said in some comment that "the first" test failed: basic_scanner. I didn't say smoketest was the only one. It's the only one done in autopkgtest though. This >turned out to be https://gcc.gnu.org/PR92267, causing an ABI breakage >in >cppunit. The fix is now in -16. Ok. Will try. Then I can add build-conflcts or so and reenable the tests. >So a symbols file and a test rebuild should have at least flagged >something, however cppunit doesn't have symbols files, because the >package >maintainer doesn't like them. For C++ and the mangling and handling it in all arxgs, yes. > And afaik there was no test rebuild for bullseye >l either. It does not help to blame people for not doing a rebuild when there is no rebuild necessary. Regards Rene -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
Re: Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)
On 29.10.19 15:09, Vincent Lefevre wrote: On 2019-10-29 13:09:46 +0100, rene.engelh...@mailbox.org wrote: Am 29. Oktober 2019 12:49:44 MEZ schrieb Vincent Lefevre : In case makefile magic triggers some rebuild, you can also run the generated executable directly (with the right environment variables, in case this matters). If the programs honors the system ABI, this is allowed, and you'll effectively test the new libstdc++6. No, if the rebuild rebuilds cppunittester or one of the exceptionprotectors or the smoketest so or similar we are at the same situation as with the autopkgtest (that's what it builds) and are not sure whether it's g++-9 or libstdc++6. Neither LO nor the test are an executable it's a executable with gazillions of .sos. I meant running the generated program (smoketest) without rebuilding it: 1. Build smoketest with the old g++-9 / libstdc++6. 2. Upgrade g++-9 / libstdc++6. 3. Run smoketest directly. (I assume that the smoketest executable does not invoke g++-9 to rebuild things on the fly.) I'm not sure if Rene wants to help tracking this down, he just disabled running the test in https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/99764f8d0df2f40aba9a220a8a4858d3f6d05494 and introducing a typo in https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/998c3b1c63bbedf8d886227749279d7ccb26a30b So maybe don't commit if you are angry. <_rene_> how supported is clang on the various (release) archs? <_rene_> completely? <_rene_> (clang++ if it matters) <_rene_> (actually probably only matters for amd64/arm64 for now, but...) so I assume we cannot expect Rene's help for that issue anymore. The comment about cppunit made me look at the cppunit package to find #935902, and yes, the test case is reproducible. So looking at the test failure would have been revealed that the test frame work is broken, not a single test. This turned out to be https://gcc.gnu.org/PR92267, causing an ABI breakage in cppunit. The fix is now in -16. So a symbols file and a test rebuild should have at least flagged something, however cppunit doesn't have symbols files, because the package maintainer doesn't like them. And afaik there was no test rebuild for bullseye either. The upstream issue was introduced in May, I don't know why it's only seen now.
