Source: dnf Version: 4.14.0-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<<PKGBUILDDIR>>/build' > Running tests... > /usr/bin/ctest --force-new-ctest-process -VV > UpdateCTestConfiguration from :/<<PKGBUILDDIR>>/build/DartConfiguration.tcl > UpdateCTestConfiguration from :/<<PKGBUILDDIR>>/build/DartConfiguration.tcl > Test project /<<PKGBUILDDIR>>/build > Constructing a list of tests > Done constructing a list of tests > Updating test list for fixtures > Added 0 tests to meet fixture requirements > Checking test dependency graph... > Checking test dependency graph end > test 1 > Start 1: test > > 1: Test command: /usr/bin/python3 "-m" "unittest" "discover" "-s" "tests" > "-t" "/<<PKGBUILDDIR>>" > 1: Working Directory: /<<PKGBUILDDIR>> > 1: Environment variables: > 1: PYTHONPATH=/<<PKGBUILDDIR>>/ > 1: ASAN_OPTIONS=verify_asan_link_order=0,detect_leaks=0 > 1: Test timeout computed to be: 10000000 > 1: ....History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > 1: ......History database cannot be created, using in-memory database > instead: SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to > open database file > 1: ...History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > 1: .History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > 1: .History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > 1: ...History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > 1: .History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > 1: .History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > 1: ......Package tour not installed, cannot downgrade it. > 1: ....Package tour not installed, cannot update it. > 1: .......History database cannot be created, using in-memory database > instead: SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to > open database file > 1: > ....................................................................................................................................................................................................................................................................................... > 1/1 Test #1: test .............................***Exception: SegFault 4.09 > sec > ....History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > ......History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > ...History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > .History database cannot be created, using in-memory database instead: SQLite > error on "/tmp/tests/history.sqlite": Open failed: unable to open database > file > .History database cannot be created, using in-memory database instead: SQLite > error on "/tmp/tests/history.sqlite": Open failed: unable to open database > file > ...History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > .History database cannot be created, using in-memory database instead: SQLite > error on "/tmp/tests/history.sqlite": Open failed: unable to open database > file > .History database cannot be created, using in-memory database instead: SQLite > error on "/tmp/tests/history.sqlite": Open failed: unable to open database > file > ......Package tour not installed, cannot downgrade it. > ....Package tour not installed, cannot update it. > .......History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > ....................................................................................................................................................................................................................................................................................... > > > 0% tests passed, 1 tests failed out of 1 > > Total Test time (real) = 4.10 sec > > The following tests FAILED: > 1 - test (SEGFAULT) > Errors while running CTest > make[2]: *** [Makefile:74: test] Error 8 > make[2]: Leaving directory '/<<PKGBUILDDIR>>/build' > dh_auto_test: error: cd build && make -j8 test ARGS\+=--verbose ARGS\+=-j8 > ARGS=-VV returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2023/07/26/dnf_4.14.0-4_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230726&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.
