Skip to content

The test that runs fl-dart in another directory reruns after a qemu crash too - #26

Merged
jwinarske merged 1 commit into
mainfrom
qemu-rerun-in-dir
Nov 17, 2026
Merged

jwinarske merged 1 commit into
mainfrom
qemu-rerun-in-dir

Conversation

@jwinarske

Copy link
Copy Markdown
Owner

The riscv64 cross lane failed on main at the #24 merge:

program_named_relative_to_the_working_directory
qemu-riscv64: QEMU internal SIGSEGV {code=MAPERR, addr=0x20}

That is the emulator crashing in its own code, the case common::fl_dart reruns once for. This test built its own command to set a working directory, so it had no rerun.

  • common::fl_dart_in(dir, args): fl_dart in a directory, with the same single rerun
  • The test uses it

Test harness only. The failed job is re-running on main meanwhile.

…rash too

- program_named_relative_to_the_working_directory built its own command,
  so it had none of the harness's one rerun when qemu-user crashes in
  its own code. The riscv64 cross lane failed on main at 7bf45e6 with
  that crash ("QEMU internal SIGSEGV {code=MAPERR, addr=0x20}", the
  signature the harness names), and with it no board kit was made
- common::fl_dart_in runs fl-dart in a directory with the same rerun;
  fl_dart is it with none
- review: test harness only. A fault in fl-dart is a guest signal and
  never carries the emulator's text, and a second crash still fails

Signed-off-by: Joel Winarske <joel.winarske@linux.com>
@jwinarske
jwinarske merged commit 2ee3c86 into main Nov 17, 2026
11 checks passed
@jwinarske
jwinarske deleted the qemu-rerun-in-dir branch November 17, 2026 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant