Bug#947089: marked as done (uftrace: blocked migration to testing: autopkgtest times out on arm64 and FTBFS on armhf)

2020-04-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Apr 2020 14:35:21 +
with message-id 
and subject line Bug#947089: fixed in uftrace 0.9.4-0.2
has caused the Debian Bug report #947089,
regarding uftrace: blocked migration to testing: autopkgtest times out on arm64 
and FTBFS on armhf
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.)


-- 
947089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uftrace
Version: 0.9.3-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
Tags: ftbfs
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of uftrace you added an autopkgtest to uftrace,
great. However, it fails due to timeout on arm64. Currently this failure
is blocking the migration to testing [1]. Additionally the package fails
to armhf [2]. The amd64 binary upload can be fixed by a binNMU, but we
prefer source only uploads nowadays. Can you please investigate the
situation and fix the arm64 autopkgtest timeout and armhf ftbfs?

Paul

[1] https://qa.debian.org/excuses.php?package=uftrace

[2]
Tail of log for uftrace on armhf:

gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time
-D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<>
-iquote /<>/arch/arm -W -Wall -Wno-unused-parameter
-Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE
-DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW
-DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE
-D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW  -DHAVE_LIBCAPSTONE
-I/usr/include/capstone   -fPIC -fvisibility=hidden
-fno-omit-frame-pointer -c -o
/<>/libmcount/symbol-libelf.op
/<>/utils/symbol-libelf.c
gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time
-D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<>
-iquote /<>/arch/arm -W -Wall -Wno-unused-parameter
-Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE
-DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW
-DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE
-D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW  -DHAVE_LIBCAPSTONE
-I/usr/include/capstone   -fPIC -fvisibility=hidden
-fno-omit-frame-pointer -c -o /<>/libmcount/symbol.op
/<>/utils/symbol.c
gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time
-D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<>
-iquote /<>/arch/arm -W -Wall -Wno-unused-parameter
-Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE
-DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW
-DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE
-D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW  -DHAVE_LIBCAPSTONE
-I/usr/include/capstone   -fPIC -fvisibility=hidden
-fno-omit-frame-pointer -c -o /<>/arch/arm/mcount.op
/<>/arch/arm/mcount.S
gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time
-D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<>
-iquote /<>/arch/arm -W -Wall -Wno-unused-parameter
-Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE
-DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW
-DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE
-D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW  -DHAVE_LIBCAPSTONE
-I/usr/include/capstone   -fPIC -fvisibility=hidden
-fno-omit-frame-pointer -c -o /<>/arch/arm/plthook.op
/<>/arch/arm/plthook.S
gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time
-D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<>
-iquote /<>/arch/arm -W -Wall -Wno-unused-parameter
-Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE
-DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW
-DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE
-D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW  -DHAVE_LIBCAPSTONE
-I/usr/include/capstone   -fPIC -fvisibility=hidden
-fno-omit-frame-pointer -c -o
/<>/arch/arm/mcount-support.op
/<>/arch/arm/mcount-support.c
/<>/arch/arm/mcount-support.c: In function
‘mcount_arch_parent_location’:
/<>/arch/arm/mcount-support.c:289:2: error: ‘cache’
undeclared (first use in this function)
  289 |  cache = lookup_cache(_cache, sym->addr, true);
  |  ^
/<>/arch/arm/mcount-support.c:289:2: note: each undeclared
identifier is reported only once for each function it appears in
make[2]: *** [Makefile:28: /<>/arch/arm/mcount-support.op]
Error 1
make[1]: *** [Makefile:242: /<>/arch/arm/mcount-entry.op]
Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:14: binary-arch] Error 255



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: uftrace
Source-Version: 0.9.4-0.2
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version 

Bug#947089: marked as done (uftrace: blocked migration to testing: autopkgtest times out on arm64 and FTBFS on armhf)

2020-04-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Apr 2020 20:49:53 +
with message-id 
and subject line Bug#947089: fixed in uftrace 0.9.4-0.1
has caused the Debian Bug report #947089,
regarding uftrace: blocked migration to testing: autopkgtest times out on arm64 
and FTBFS on armhf
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.)


-- 
947089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uftrace
Version: 0.9.3-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
Tags: ftbfs
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of uftrace you added an autopkgtest to uftrace,
great. However, it fails due to timeout on arm64. Currently this failure
is blocking the migration to testing [1]. Additionally the package fails
to armhf [2]. The amd64 binary upload can be fixed by a binNMU, but we
prefer source only uploads nowadays. Can you please investigate the
situation and fix the arm64 autopkgtest timeout and armhf ftbfs?

Paul

[1] https://qa.debian.org/excuses.php?package=uftrace

[2]
Tail of log for uftrace on armhf:

gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time
-D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<>
-iquote /<>/arch/arm -W -Wall -Wno-unused-parameter
-Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE
-DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW
-DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE
-D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW  -DHAVE_LIBCAPSTONE
-I/usr/include/capstone   -fPIC -fvisibility=hidden
-fno-omit-frame-pointer -c -o
/<>/libmcount/symbol-libelf.op
/<>/utils/symbol-libelf.c
gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time
-D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<>
-iquote /<>/arch/arm -W -Wall -Wno-unused-parameter
-Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE
-DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW
-DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE
-D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW  -DHAVE_LIBCAPSTONE
-I/usr/include/capstone   -fPIC -fvisibility=hidden
-fno-omit-frame-pointer -c -o /<>/libmcount/symbol.op
/<>/utils/symbol.c
gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time
-D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<>
-iquote /<>/arch/arm -W -Wall -Wno-unused-parameter
-Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE
-DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW
-DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE
-D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW  -DHAVE_LIBCAPSTONE
-I/usr/include/capstone   -fPIC -fvisibility=hidden
-fno-omit-frame-pointer -c -o /<>/arch/arm/mcount.op
/<>/arch/arm/mcount.S
gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time
-D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<>
-iquote /<>/arch/arm -W -Wall -Wno-unused-parameter
-Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE
-DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW
-DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE
-D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW  -DHAVE_LIBCAPSTONE
-I/usr/include/capstone   -fPIC -fvisibility=hidden
-fno-omit-frame-pointer -c -o /<>/arch/arm/plthook.op
/<>/arch/arm/plthook.S
gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time
-D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<>
-iquote /<>/arch/arm -W -Wall -Wno-unused-parameter
-Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE
-DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW
-DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE
-D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW  -DHAVE_LIBCAPSTONE
-I/usr/include/capstone   -fPIC -fvisibility=hidden
-fno-omit-frame-pointer -c -o
/<>/arch/arm/mcount-support.op
/<>/arch/arm/mcount-support.c
/<>/arch/arm/mcount-support.c: In function
‘mcount_arch_parent_location’:
/<>/arch/arm/mcount-support.c:289:2: error: ‘cache’
undeclared (first use in this function)
  289 |  cache = lookup_cache(_cache, sym->addr, true);
  |  ^
/<>/arch/arm/mcount-support.c:289:2: note: each undeclared
identifier is reported only once for each function it appears in
make[2]: *** [Makefile:28: /<>/arch/arm/mcount-support.op]
Error 1
make[1]: *** [Makefile:242: /<>/arch/arm/mcount-entry.op]
Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:14: binary-arch] Error 255



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: uftrace
Source-Version: 0.9.4-0.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version