Bug#963546: meson: autopkgtest failures
On Fri, 26 Jun 2020 at 14:09, Gianfranco Costamagna wrote: > > > I asked in Ubuntu to move the meson autopkgtests to a machine with more > > > ram memory, and > > > now the test passes. > > > The Ubuntu VMs have 1536MB of ram, probably not enough for the testsuite > > > to pass. > > > > Good that it works, but that seems a bit strange. I run the test suite > > on an x86 Debian VM with 4 gigs of ram and it passes without problems. > > Probably if you lower the 4GB to 1.5GB you will get the same failure? D'oh! I accidentally read that as 15 GB rather than 1.5GB because I blindly assumed that there is no way the default value can be that low. Compiling e.g. any C++ program of decent size makes the linker take several gigabytes of ram easily.
Bug#963546: meson: autopkgtest failures
On Fri, 26 Jun 2020 11:38:34 +0300 Jussi Pakkanen wrote: > On Fri, 26 Jun 2020 at 10:48, Gianfranco Costamagna > wrote: > > > I asked in Ubuntu to move the meson autopkgtests to a machine with more ram > > memory, and > > now the test passes. > > The Ubuntu VMs have 1536MB of ram, probably not enough for the testsuite to > > pass. > > Good that it works, but that seems a bit strange. I run the test suite > on an x86 Debian VM with 4 gigs of ram and it passes without problems. > > Probably if you lower the 4GB to 1.5GB you will get the same failure? IIRC when I tried with a value around 2GB everything was good... G.
Bug#963546: meson: autopkgtest failures
On Fri, 26 Jun 2020 at 10:48, Gianfranco Costamagna wrote: > I asked in Ubuntu to move the meson autopkgtests to a machine with more ram > memory, and > now the test passes. > The Ubuntu VMs have 1536MB of ram, probably not enough for the testsuite to > pass. Good that it works, but that seems a bit strange. I run the test suite on an x86 Debian VM with 4 gigs of ram and it passes without problems.
Bug#963546: meson: autopkgtest failures
Hello, > > Interesting, this might explain also why I cannot replicate it under a > pbuilder environment... > Can we try to lower the ninja parallelism to see if the build ends correctly? > I suspect this might be an issue with Debian too, in the near future (e.g. > new gcc-10 defaults) > I asked in Ubuntu to move the meson autopkgtests to a machine with more ram memory, and now the test passes. The Ubuntu VMs have 1536MB of ram, probably not enough for the testsuite to pass. I hope Debian won't have the same problem in the near future, but for now the problem in Ubuntu is solved. G.
Bug#963546: meson: autopkgtest failures
Hello, On Wed, 24 Jun 2020 02:08:23 +0300 Jussi Pakkanen wrote: > On Tue, 23 Jun 2020 at 16:36, Gianfranco Costamagna > wrote: > > > Hello, as you can see, two tests can't be run on ppc64el and s390x, because > > of missing: > > g++-arm-linux-gnueabihf and ldc > > https://ci.debian.net/data/autopkgtest/unstable/ppc64el/m/meson/6017346/log.gz > > Marking the two tests as "skip-not-installed" works > > Thanks, this will be in the next upload. double thanks! > > > Also, I noticed a failure on Ubuntu: > > c++ -Iextralibexe@exe -I. '-I../test cases/frameworks/1 boost' > > -I/usr/include -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 > > -Wall -Winvalid-pch -Wnon-virtual-dtor -std=c++14 -g -pthread > > -DBOOST_DATE_TIME_DYN_LINK=1 -DBOOST_FILESYSTEM_DYN_LINK=1 > > -DBOOST_LOG_SETUP_DYN_LINK=1 -DBOOST_THREAD_BUILD_DLL=1 > > -DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_THREAD_USE_DLL=1 -DBOOST_LOG_DYN_LINK=1 > > -DBOOST_ALL_NO_LIB -MD -MQ 'extralibexe@exe/extralib.cpp.o' -MF > > 'extralibexe@exe/extralib.cpp.o.d' -o 'extralibexe@exe/extralib.cpp.o' -c > > '../test cases/frameworks/1 boost/extralib.cpp' > > c++: fatal error: Killed signal terminated program cc1plus > > > > do you have any clue? > > At this point Meson is no longer involved. Ninja has invoked c++ and > that process then crashes. Running that command by hand in the same > system should result in the same crash. > > From what I can tell this is either a bug in GCC or there is some > watchdog that kills the process for whatever reason such as running > out of memory. The latter can be a symptom of the former. > Interesting, this might explain also why I cannot replicate it under a pbuilder environment... Can we try to lower the ninja parallelism to see if the build ends correctly? I suspect this might be an issue with Debian too, in the near future (e.g. new gcc-10 defaults) G.
Bug#963546: meson: autopkgtest failures
On Tue, 23 Jun 2020 at 16:36, Gianfranco Costamagna wrote: > Hello, as you can see, two tests can't be run on ppc64el and s390x, because > of missing: > g++-arm-linux-gnueabihf and ldc > https://ci.debian.net/data/autopkgtest/unstable/ppc64el/m/meson/6017346/log.gz > Marking the two tests as "skip-not-installed" works Thanks, this will be in the next upload. > Also, I noticed a failure on Ubuntu: > c++ -Iextralibexe@exe -I. '-I../test cases/frameworks/1 boost' -I/usr/include > -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch > -Wnon-virtual-dtor -std=c++14 -g -pthread -DBOOST_DATE_TIME_DYN_LINK=1 > -DBOOST_FILESYSTEM_DYN_LINK=1 -DBOOST_LOG_SETUP_DYN_LINK=1 > -DBOOST_THREAD_BUILD_DLL=1 -DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_THREAD_USE_DLL=1 > -DBOOST_LOG_DYN_LINK=1 -DBOOST_ALL_NO_LIB -MD -MQ > 'extralibexe@exe/extralib.cpp.o' -MF 'extralibexe@exe/extralib.cpp.o.d' -o > 'extralibexe@exe/extralib.cpp.o' -c '../test cases/frameworks/1 > boost/extralib.cpp' > c++: fatal error: Killed signal terminated program cc1plus > > do you have any clue? At this point Meson is no longer involved. Ninja has invoked c++ and that process then crashes. Running that command by hand in the same system should result in the same crash. >From what I can tell this is either a bug in GCC or there is some watchdog that kills the process for whatever reason such as running out of memory. The latter can be a symptom of the former.
Bug#963546: meson: autopkgtest failures
Source: meson Version: 0.54.3-1 Severity: serious Hello, as you can see, two tests can't be run on ppc64el and s390x, because of missing: g++-arm-linux-gnueabihf and ldc https://ci.debian.net/data/autopkgtest/unstable/ppc64el/m/meson/6017346/log.gz Marking the two tests as "skip-not-installed" works diff -Nru meson-0.54.3/debian/tests/control meson-0.54.3/debian/tests/control --- meson-0.54.3/debian/tests/control 2020-03-27 23:40:23.0 + +++ meson-0.54.3/debian/tests/control 2020-06-23 13:25:22.0 + @@ -10,6 +10,8 @@ # tests are run and thus block broken uploads. Tests: exhaustive Depends: meson, @builddeps@, valac, rustc, ldc +Restrictions: skip-not-installable Tests: crossbuild Depends: meson, g++, g++-arm-linux-gnueabihf +Restrictions: skip-not-installable Also, I noticed a failure on Ubuntu: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/m/meson/20200616_020946_f376b@/log.gz Failed test during build: 'test cases/frameworks/1 boost (static=false)' Reason: Compiling source code failed. Skipping: test cases/frameworks/1 boost (static=false b_vscrt=md) Skipping: test cases/frameworks/1 boost (static=false b_vscrt=mdd) Succeeded test: test cases/frameworks/1 boost (static=true) Skipping: test cases/frameworks/1 boost (static=true b_vscrt=md) Skipping: test cases/frameworks/1 boost (static=true b_vscrt=mdd) Skipping: test cases/frameworks/1 boost (static=true b_vscrt=mt) Skipping: test cases/frameworks/1 boost (static=true b_vscrt=mtd) Mesonlogs of failing tests The Meson build system Version: 0.54.3 Source dir: /tmp/autopkgtest.u568ol/build.zhB/src/test cases/frameworks/1 boost Build dir: /tmp/autopkgtest.u568ol/build.zhB/src/b 125f976e40 Build type: native build Project name: boosttest Project version: undefined C++ compiler for the host machine: c++ (gcc 9.3.0 "c++ (Ubuntu 9.3.0-13ubuntu1) 9.3.0") C++ linker for the host machine: c++ ld.bfd 2.34 Host machine cpu family: x86_64 Host machine cpu: x86_64 Found pkg-config: /usr/bin/pkg-config (0.29.2) Run-time dependency Boost found: YES 1.71.0 (/usr/include) Run-time dependency Boost (found: date_time, system, thread) found: YES 1.71.0 (/usr) Run-time dependency Boost (found: unit_test_framework) found: YES 1.71.0 (/usr) Dependency boost found: YES 1.71.0 (cached) Run-time dependency Boost (found: date_time, filesystem, log, log_setup, regex, system, thread) found: YES 1.71.0 (/usr) Run-time dependency Boost (missing: this_should_not_exist_on_any_systen) found: NO Program python2 found: YES (/usr/bin/python2) Program python3 found: YES (/usr/bin/python3) test cases/frameworks/1 boost/meson.build:27: WARNING: Passed invalid keyword argument "disabler". WARNING: This will become a hard error in the future. Dependency python found: NO test cases/frameworks/1 boost/meson.build:28: WARNING: Passed invalid keyword argument "disabler". WARNING: This will become a hard error in the future. Dependency python found: YES (pkgconfig) Run-time dependency Boost (found: python38) found: YES 1.71.0 (/usr) Program /usr/bin/python2 found: YES (/usr/bin/python2) Program /usr/bin/python3 found: YES (/usr/bin/python3) Run-time dependency Boost found: YES 1.71.0 (/usr/include) Dependency boost found: YES 1.71.0 (cached) Build targets in project: 7 Found ninja-1.10.0 at /usr/bin/ninja [1/14] Compiling C++ object 'utf@exe/unit_test.cpp.o' [2/14] Linking target utf [3/14] Compiling C++ object 'nomod@exe/nomod.cpp.o' [4/14] Linking target nomod [5/14] Compiling C++ object 'linkedexe@exe/linkexe.cc.o' [6/14] Linking target linkedexe [7/14] Compiling C++ object 'extralibexe@exe/extralib.cpp.o' FAILED: extralibexe@exe/extralib.cpp.o c++ -Iextralibexe@exe -I. '-I../test cases/frameworks/1 boost' -I/usr/include -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -std=c++14 -g -pthread -DBOOST_DATE_TIME_DYN_LINK=1 -DBOOST_FILESYSTEM_DYN_LINK=1 -DBOOST_LOG_SETUP_DYN_LINK=1 -DBOOST_THREAD_BUILD_DLL=1 -DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_THREAD_USE_DLL=1 -DBOOST_LOG_DYN_LINK=1 -DBOOST_ALL_NO_LIB -MD -MQ 'extralibexe@exe/extralib.cpp.o' -MF 'extralibexe@exe/extralib.cpp.o.d' -o 'extralibexe@exe/extralib.cpp.o' -c '../test cases/frameworks/1 boost/extralib.cpp' c++: fatal error: Killed signal terminated program cc1plus compilation terminated. [8/14] Compiling C++ object 'python3_module@sha/python_module.cpp.o' ninja: build stopped: subcommand failed. ninja explain: deps for 'linkedexe@exe/linkexe.cc.o' are missing ninja explain: linkedexe@exe/linkexe.cc.o is dirty ninja explain: linkedexe is dirty ninja explain: deps for 'utf@exe/unit_test.cpp.o' are missing ninja explain: utf@exe/unit_test.cpp.o is dirty ninja explain: utf is dirty ninja explain: deps for 'nomod@exe/nomod.cpp.o' are missing ninja explain: nomod@exe/nomod.cpp.o is dirty ninja explain: nomod is dirty ninja explain: deps for
