Public bug reported:
strace started to FTBFS on armhf against that version, but was building
fine against 2.42-0ubuntu1.
Excerpt from the failing builds (first failing test):
--- /dev/null 2025-08-02 18:23:40.000000000 +0000
+++ log 2025-09-22 15:40:20.824144876 +0000
@@ -0,0 +1 @@
+clock_gettime64(CLOCK_MONOTONIC, {tv_sec=398, tv_nsec=625531646}) = 0
+ fail_ ../../src/strace -qq -esignal=none -e/clock ../getgid output mismatch
+ warn_ clock.gen.test: failed test: ../../src/strace -qq -esignal=none
-e/clock ../getgid output mismatch
+ printf %s\n clock.gen.test: failed test: ../../src/strace -qq -esignal=none
-e/clock ../getgid output mismatch
clock.gen.test: failed test: ../../src/strace -qq -esignal=none -e/clock
../getgid output mismatch
+ exit 1
FAIL clock.gen.test (exit status: 1)
** Affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Affects: strace (Ubuntu)
Importance: Undecided
Status: New
** Tags: dcr-incoming ftbfs
** Also affects: strace (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2125424
Title:
strace FTBFS against glibc 2.42-0ubuntu3 on armhf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2125424/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
