Open evrim opened 1 year ago
Is this always reproducible?
Found nonzero at ... - allocator is broken
I haven't seen such an error yet. Thank you for reporting. Would be nice to investigate the root cause.
Please also check on master.
Sorry to bump this -- I'm able to reproduce with 8.2.2, 8.2.4, and master (4306149f0bea951a9fb2c967a7b01c292c8aa78f).
boehm-gc-aarch64-linux> ================================
boehm-gc-aarch64-linux> gc 8.3.0: ./test-suite.log
boehm-gc-aarch64-linux> ================================
boehm-gc-aarch64-linux>
boehm-gc-aarch64-linux> # TOTAL: 17
boehm-gc-aarch64-linux> # PASS: 16
boehm-gc-aarch64-linux> # SKIP: 0
boehm-gc-aarch64-linux> # XFAIL: 0
boehm-gc-aarch64-linux> # FAIL: 1
boehm-gc-aarch64-linux> # XPASS: 0
boehm-gc-aarch64-linux> # ERROR: 0
boehm-gc-aarch64-linux>
boehm-gc-aarch64-linux> .. contents:: :depth: 2
boehm-gc-aarch64-linux>
boehm-gc-aarch64-linux> FAIL: gctest
boehm-gc-aarch64-linux> ============
boehm-gc-aarch64-linux>
boehm-gc-aarch64-linux> Switched to incremental mode
boehm-gc-aarch64-linux> Emulating dirty bits with mprotect/signals
boehm-gc-aarch64-linux> **
boehm-gc-aarch64-linux> ERROR:../plugins/core.c:221:qemu_plugin_vcpu_init_hook: assertion failed: (success)
boehm-gc-aarch64-linux> Bail out! ERROR:../plugins/core.c:221:qemu_plugin_vcpu_init_hook: assertion failed: (success)
boehm-gc-aarch64-linux> **
boehm-gc-aarch64-linux> ERROR:../accel/tcg/cpu-exec.c:532:cpu_exec_longjmp_cleanup: assertion failed: (cpu == current_cpu)
boehm-gc-aarch64-linux> Bail out! ERROR:../accel/tcg/cpu-exec.c:532:cpu_exec_longjmp_cleanup: assertion failed: (cpu == current_cpu)
boehm-gc-aarch64-linux> Child process failed, pid= 15699, status= 0x7f00
boehm-gc-aarch64-linux> Test failed
boehm-gc-aarch64-linux> qemu: uncaught target signal 6 (Aborted) - core dumped
boehm-gc-aarch64-linux> FAIL gctest (exit status: 134)
boehm-gc-aarch64-linux>
boehm-gc-aarch64-linux> ============================================================================
boehm-gc-aarch64-linux> Testsuite summary for gc 8.3.0
boehm-gc-aarch64-linux> ============================================================================
boehm-gc-aarch64-linux> # TOTAL: 17
boehm-gc-aarch64-linux> # PASS: 16
boehm-gc-aarch64-linux> # SKIP: 0
boehm-gc-aarch64-linux> # XFAIL: 0
boehm-gc-aarch64-linux> # FAIL: 1
boehm-gc-aarch64-linux> # XPASS: 0
boehm-gc-aarch64-linux> # ERROR: 0
boehm-gc-aarch64-linux> ============================================================================
boehm-gc-aarch64-linux> See ./test-suite.log
boehm-gc-aarch64-linux> Please report to https://github.com/ivmai/bdwgc/issues
boehm-gc-aarch64-linux> ============================================================================
boehm-gc-aarch64-linux> make[3]: *** [Makefile:2068: test-suite.log] Error 1
boehm-gc-aarch64-linux> make[3]: Leaving directory '/build/source'
boehm-gc-aarch64-linux> make[2]: *** [Makefile:2176: check-TESTS] Error 2
boehm-gc-aarch64-linux> make[2]: Leaving directory '/build/source'
boehm-gc-aarch64-linux> make[1]: *** [Makefile:2532: check-am] Error 2
boehm-gc-aarch64-linux> make[1]: Leaving directory '/build/source'
boehm-gc-aarch64-linux> make: *** [Makefile:1953: check-recursive] Error 1
Thank you for reporting! What is signal 6? Has child process failed because of Qemu issue? Do you have any insights about the failure?
Unfortunately I have no ideas about what signal 6 could be or if it's an issue with Qemu.
I'm using NixOS on x86_64-linux
with Qemu to emulate an aarch64-linux
builder: https://github.com/ConnorBaker/nixos-configs/blob/47d40f6f060a000c4dbe0fe412c102e163df52be/devices/nixos-desktop/hardware.nix#L5.
For the moment I've worked around this by disabling the check phase (https://github.com/ConnorBaker/nixos-configs/blob/47d40f6f060a000c4dbe0fe412c102e163df52be/nixpkgs-overlays.nix#L11-L19), but that causes a large rebuild of a bunch of Nixpkgs.
Hello,
8.2.2 tests fail on aarch64 while I was trying to cross compile over qemu 7.2.0. Not sure if this is related to some other bug, just link if thats the case.
best, evrim.