error: process didn't exit successfully: bootimage runner target\x86_64-eduos\debug\eduos-rs (exit code: 5)

[FutureDragon]

I have tried stage0, 8, 7, and all getting the error:
error: process didn't exit successfully: bootimage runner target\x86_64-eduos\debug\eduos-rs (exit code: 5)

I am running from Windows 11.

Below is the complete cargo run ouput:

cargo run
Compiling compiler_builtins v0.1.82
Compiling core v0.0.0 (C:\Users\xxxxx.rustup\toolchains\nightly-2022-11-11-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core)
Compiling bootloader v0.9.23
Compiling lock_api v0.4.9
Compiling x86 v0.52.0
Compiling rustc-std-workspace-core v1.99.0 (C:\Users\xxxxx.rustup\toolchains\nightly-2022-11-11-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\rustc-std-workspace-core)
Compiling alloc v0.0.0 (C:\Users\xxxxx.rustup\toolchains\nightly-2022-11-11-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\alloc)
Compiling bitflags v1.3.2
Compiling scopeguard v1.1.0
Compiling bit_field v0.10.1
Compiling qemu-exit v3.0.1
Compiling raw-cpuid v10.6.0
Compiling spin v0.9.4
Compiling eduos-rs v0.1.0 (C:\Users\xxxxx\source\repos\eduOS-rs)
Finished dev [unoptimized + debuginfo] target(s) in 23.85s
Running bootimage runner target\x86_64-eduos\debug\eduos-rs
Building bootloader
Compiling bootloader v0.9.23 (C:\Users\xxxxx.cargo\registry\src\github.com-1ecc6299db9ec823\bootloader-0.9.23)
Finished release [optimized + debuginfo] target(s) in 3.84s
Running: qemu-system-x86_64 -display none -smp 1 -m 128M -serial stdio -cpu qemu64,apic,fsgsbase,rdtscp,xsave,xsaveopt,fxsr -device isa-debug-exit,iobase=0xf4,iosize=0x04 -drive format=raw,file=target\x86_64-eduos\debug\bootimage-eduos-rs.bin
Hello world!
error: process didn't exit successfully: bootimage runner target\x86_64-eduos\debug\eduos-rs (exit code: 5)

[stlankes]

I think that the issue is already fixed. At least the Windows CI is able to run the kernel successfully.

[stlankes]

My mistake, it is still an issue. I will take a look into it.

[stlankes]

Ah, now I understand. I forgot that we return 5, if we terminate correctly. In case of UNIX, we check the return value by a script. I should write a similar script for Windows.

[stlankes]

I wrote already a script. The CI use the script to test the error code. However, the error message is still seeable. Do you have any idea how I can avoid this?