On 1/28/25 15:19, Stefan Hajnoczi wrote:
thread '<unnamed>' panicked at 'already borrowed',
rust/qemu-api/libqemu_api.rlib.p/structured/cell.rs:450:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
https://gitlab.com/qemu-project/qemu/-/jobs/8972076251/artifacts/browse/build/tests/functional/arm/test_arm_tuxrun.TuxRunArmTest.test_armv7be/
Hmm, this one does not reproduce locally. I've started a
QEMU_CI_AVOCADO_TESTING run.
Do you want to include a patch that sets RUST_BACKTRACE=1 in the test
environment so the backtrace is captured in the logs?
Yeah, I'll send one in the next version of the pull request. The
BqlRefCell issues are easy to track (because you cannot drop the BQL
while you have an outstanding borrow, unlike regular Rust RefCells), but
you do need a backtrace...
Paolo