Bug#1103126: mdds: FTBFS in testing/i386: make[8]: *** [Makefile:698: test-suite.log] Error 1
Source: mdds
Version: 2.1.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lucas@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):
> make[8]: Entering directory '/build/reproducible-path/mdds-2.1.1/test/multi_type_vector/collection/aos'
> ../../../../test-driver: line 112: 4355 Aborted "$@" >> "$log_file" 2>&1
> FAIL: test-main
> ============================================================================
> Testsuite summary for mdds 2.1.1
> ============================================================================
> # TOTAL: 1
> # PASS: 0
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
> ============================================================================
> See test/multi_type_vector/collection/aos/test-suite.log for debugging.
> Some test(s) failed. Please report this to kohei.yoshida@gmail.com,
> together with the test-suite.log file (gzipped) and your system
> information. Thanks.
> ============================================================================
> make[8]: *** [Makefile:698: test-suite.log] Error 1
The full build log is available from:
http://qa-logs.debian.net/2025/04/14/mdds_2.1.1-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=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250414&fusertaguser=lucas@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.
Reply to: