Zig Version
0.11.0-dev.2146+9964f1c16
Steps to Reproduce and Observed Behavior
Currently when running custom steps, all are run at the same time. If have a child process executing QEMU and two instances of QEMU are run at the same time, the second instance would error with something in the lines of:
qemu-system-x86_64: Failed to get "write" lock
Is another process using the image [zig-cache/rise_ReleaseFast_x86_64_rise_bios_test.hdd]?
I suppose the Zig user (the programmer of such project) could handle this, but I think it would be very tedious to do.
Expected Behavior
One should be able to specify for a particular step not to be run in parallel, but one at a time. Another reason why this would be annoying even if it was possible to do it is that you get logs mixed.
Zig Version
0.11.0-dev.2146+9964f1c16
Steps to Reproduce and Observed Behavior
Currently when running custom steps, all are run at the same time. If have a child process executing QEMU and two instances of QEMU are run at the same time, the second instance would error with something in the lines of:
I suppose the Zig user (the programmer of such project) could handle this, but I think it would be very tedious to do.
Expected Behavior
One should be able to specify for a particular step not to be run in parallel, but one at a time. Another reason why this would be annoying even if it was possible to do it is that you get logs mixed.