Your message dated Sun, 28 Apr 2024 11:57:58 +0200 with message-id <20240428095758.x2v7o6l6l4ivtvzj@begin> and subject line Re: Bug#1069433: gtg-trace: FTBFS on armhf: tests fail has caused the Debian Bug report #1069433, regarding gtg-trace: FTBFS on armhf: tests fail to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1069433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: gtg-trace Version: 0.2-3-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf Hi, During a rebuild of all packages in sid, your package failed to build on armhf. Relevant part (hopefully): > make[2]: Entering directory '/<<PKGBUILDDIR>>/test' > mkdir -p bin > mpicc testState.c -o bin/testState -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I../inc -Wl,-z,relro > -L../src/.libs -lgtg > mpicc testEvent.c -o bin/testEvent -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I../inc -Wl,-z,relro > -L../src/.libs -lgtg > mpicc testLink.c -o bin/testLink -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 > -I../inc -Wl,-z,relro -L../src/.libs -lgtg > mpicc testVar.c -o bin/testVar -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 > -I../inc -Wl,-z,relro -L../src/.libs -lgtg > mpicc testAll.c -o bin/testAll -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 > -I../inc -Wl,-z,relro -L../src/.libs -lgtg > mpicc testState_parall.c -o bin/testState_parall -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I../inc -Wl,-z,relro > -L../src/.libs -lgtg > mpicc testEvent_parall.c -o bin/testEvent_parall -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I../inc -Wl,-z,relro > -L../src/.libs -lgtg > mpicc testEvent_mpi.c -o bin/testEvent_mpi -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I../inc -Wl,-z,relro > -L../src/.libs -lgtg > for i in testState testEvent testLink testVar testAll ; do \ > for type in 1 2 ; do \ > echo running $i $type ; \ > bin/$i $type ; \ > done ; \ > done > running testState 1 > running testState 2 > running testEvent 1 > running testEvent 2 > running testLink 1 > running testLink 2 > running testVar 1 > running testVar 2 > running testAll 1 > running testAll 2 > for i in testState_parall testEvent_parall testEvent_mpi ; do \ > for type in 1 ; do \ > echo running $i $type ; \ > mpirun --host localhost:6 -np 6 bin/$i $type ; \ > done ; \ > done > running testState_parall 1 > -------------------------------------------------------------------------- > Sorry! You were supposed to get help about: > pmix_init:startup:internal-failure > But I couldn't open the help file: > /usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry! > -------------------------------------------------------------------------- > [ip-10-84-234-251:1132190] PMIX ERROR: NOT-FOUND in file > ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at > line 237 > running testEvent_parall 1 > -------------------------------------------------------------------------- > Sorry! You were supposed to get help about: > pmix_init:startup:internal-failure > But I couldn't open the help file: > /usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry! > -------------------------------------------------------------------------- > [ip-10-84-234-251:1132191] PMIX ERROR: NOT-FOUND in file > ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at > line 237 > running testEvent_mpi 1 > -------------------------------------------------------------------------- > Sorry! You were supposed to get help about: > pmix_init:startup:internal-failure > But I couldn't open the help file: > /usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry! > -------------------------------------------------------------------------- > [ip-10-84-234-251:1132192] PMIX ERROR: NOT-FOUND in file > ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at > line 237 > make[2]: *** [Makefile:48: check] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/04/20/gtg-trace_0.2-3-2_unstable-armhf.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240420&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.
--- End Message ---
--- Begin Message ---Version: 4.1.6-13 Samuel Thibault, le dim. 21 avril 2024 05:29:09 +0900, a ecrit: > This happens on i386 too, but also with the following trivial testcase > on armhf and i386: > > $ cat test.c > #include <mpi.h> > #include <stdio.h> > int main(int argc, char *argv[]) { > int size, rank; > MPI_Init(&argc, &argv); > MPI_Comm_size(MPI_COMM_WORLD, &size); > MPI_Comm_rank(MPI_COMM_WORLD, &rank); > printf("%d/%d\n", rank, size); > MPI_Finalize(); > return 0; > } > $ mpicc test.c -o test > $ mpirun -np 2 ./test > -------------------------------------------------------------------------- > Sorry! You were supposed to get help about: > pmix_init:startup:internal-failure > But I couldn't open the help file: > /usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry! > -------------------------------------------------------------------------- > [abel:25256] PMIX ERROR: NOT-FOUND in file > ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at > line 237 Confirmed to be fixed by 4.1.6-13 Samuel
--- End Message ---
