Source: cppnumericalsolvers Version: 1.0.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250414 ftbfs-trixie
Hi, During a rebuild of all packages in testing (trixie), your package failed to build on i386. Relevant part (hopefully): > debian/rules override_dh_auto_test > make[1]: Entering directory > '/build/reproducible-path/cppnumericalsolvers-1.0.0' > g++ -g -O2 > -ffile-prefix-map=/build/reproducible-path/cppnumericalsolvers-1.0.0=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 src/test/verify.cpp -o verify -I. -I/usr/include/eigen3 > -lgtest -lpthread -Wl,-z,relro > ./verify > [==========] Running 62 tests from 26 test suites. > [----------] Global test environment set-up. > [----------] 2 tests from GradientDescentTest > [ RUN ] GradientDescentTest.RosenbrockFarValue > [ OK ] GradientDescentTest.RosenbrockFarValue (4 ms) > [ RUN ] GradientDescentTest.RosenbrockNearValue > [ OK ] GradientDescentTest.RosenbrockNearValue (0 ms) > [----------] 2 tests from GradientDescentTest (4 ms total) > > [----------] 3 tests from ConjugatedGradientDescentTest > [ RUN ] ConjugatedGradientDescentTest.RosenbrockFarValue > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://qa-logs.debian.net/2025/04/14/cppnumericalsolvers_1.0.0-2_testing-i386.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20250414;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250414&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
