Skip to content

Test failures on RISC-V #55

@jsmolic

Description

@jsmolic

Hi, I'm trying to add support for RISC-V to boxfort in Gentoo. I've backported c91d718 into our package, the compilation phase looks fine, however I ran into two test failures:

==================================== 3/5 =====================================
test:         context.c
start time:   18:17:36
duration:     0.38s
result:       killed by signal 6 SIGABRT
command:      UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=166 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 MESON_TEST_ITERATION=1 /var/tmp/portage/dev-libs/boxfort-0.1.4-r1/work/boxfort-0.1.4-build/sample/context.c.bin
==============================================================================

==================================== 4/5 =====================================
test:         cram tests
start time:   18:17:36
duration:     0.79s
result:       exit status 1
command:      PATH=/var/tmp/portage/dev-libs/boxfort-0.1.4-r1/work/boxfort-0.1.4-build/test/../sample:/var/tmp/portage/dev-libs/boxfort-0.1.4-r1/work/boxfort-0.1.4-build/test/../sample:/var/tmp/portage/dev-libs/boxfort-0.1.4-r1/temp/python3.12/bin:/usr/lib/portage/python3.12/ebuild-helpers/xattr:/usr/lib/portage/python3.12/ebuild-helpers:/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/bin:/usr/lib/llvm/19/bin:/usr/lib/llvm/18/bin:/usr/lib/llvm/15/bin LC_ALL=en_US.utf8 UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=40 MSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MSYS2_ARG_CONV_EXCL=--filter= ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 TERM=dumb MESON_TEST_ITERATION=1 /usr/bin/cram --shell=/usr/bin/sh /var/tmp/portage/dev-libs/boxfort-0.1.4-r1/work/BoxFort-0.1.4/test/cram
----------------------------------- stdout -----------------------------------
!
--- /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:  2553 Aborted                 (core dumped) context.c.bin
+  [134]

# Ran 1 tests, 0 skipped, 1 failed.
==============================================================================

==================================== 5/5 =====================================
test:         timeout.c
start time:   18:17:36
duration:     2.03s
result:       exit status 0
command:      MALLOC_PERTURB_=3 UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 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 MESON_TEST_ITERATION=1 /var/tmp/portage/dev-libs/boxfort-0.1.4-r1/work/boxfort-0.1.4-build/sample/timeout.c.bin
----------------------------------- stdout -----------------------------------
Wait timed out after 1 second
Process killed after 2.0 seconds
==============================================================================


Summary of Failures:

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

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

I'll try to run using gdb later to get more info about this, in the meantime I'll also upload full build and test log.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions