Source: kitinerary Version: 22.12.3-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 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>>/obj-x86_64-linux-gnu' > Running tests... > /usr/bin/ctest --force-new-ctest-process --verbose -j1 > UpdateCTestConfiguration from > :/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/DartConfiguration.tcl > UpdateCTestConfiguration from > :/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/DartConfiguration.tcl > Test project /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu > 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 > > [...] > > The following tests FAILED: > 23 - structureddataextractortest (Failed) > 25 - htmldocumenttest (Failed) > 35 - extractortest (Failed) > Errors while running CTest > make[2]: *** [Makefile:74: test] Error 8 > make[2]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu' > dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test > ARGS\+=--verbose ARGS\+=-j1 returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2024/06/15/kitinerary_22.12.3-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240615&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.
