Bug 954148 – dev-libs/boxfort-0.1.4-r1: fails tests on arm64

• Status: CONFIRMED
• Product: Gentoo Linux

[Description Viorel Munteanu 2025-04-21 12:12:41 UTC]

Created attachment 925589 [details]
build logs and emerge --info on arm64

Summary of Failures:

3/5 context.c  FAIL            0.16s   killed by signal 6 SIGABRT
4/5 cram tests FAIL            0.41s   exit status 1

Ok:                 3   
Expected Fail:      0   
Fail:               2   
Unexpected Pass:    0   
Skipped:            0   
Timeout:            0

[Comment 1 Sam James 2025-04-22 04:10:52 UTC]

```
--- /var/tmp/portage/dev-libs/boxfort-0.1.4-r1/work/BoxFort-0.1.4/test/cram/core.t
+++ /var/tmp/portage/dev-libs/boxfort-0.1.4-r1/work/BoxFort-0.1.4/test/cram/core.t.err
@@ -12,5 +12,5 @@
 Testing if the context sample behave as expected
 
   $ context.c.bin
-  my_int = 42
-  my_long = 24
+  /usr/bin/sh: line 6:    63 Aborted                 (core dumped) context.c.bin
+  [134]

```

Wait, so it's supposed to crash, but didn't?

[Comment 2 Sam James 2025-04-22 04:11:44 UTC]

```
==================================== 3/5 =====================================
test:         context.c
start time:   19:15:52
duration:     0.16s
result:       killed by signal 6 SIGABRT
command:      MESON_TEST_ITERATION=1 UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=203 MSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 /var/tmp/portage/dev-libs/boxfort-0.1.4-r1/work/boxfort-0.1.4-build/sample/context.c.bin
```

This one looks odd. Needs running under gdb to find out which assertion fails.