There is a Heap Allocation Error of the following form that occurs in some recent CI runs:
<<<test_start>>>
tag=rename14 stime=1778183637
cmdline="rename14 "
contacts=""
analysis=exit
<<<test_output>>>
rename14 0 TINFO : Using /tmp/ltp-XXXXvaWr9F/LTP_renlx6h1x as tmpdir (tmpfs filesystem)
[ 40.493] ERROR: Oops! Panic: called `Result::unwrap()` on an `Err` value: NoMemory { context: StackInfo { stack_trace: stacktrace[not captured], task_id: Some(38181), cpu_id: CpuId(0), server_id: None, location: Some(Location { file: "/__w/asterinas/asterinas/ostd/src/mm/frame/allocator.rs", line: 115, column: 14 }) } } (at /__w/asterinas/asterinas/kernel/src/thread/kernel_thread.rs:75:62 on task 38181 on cpu 0 with stack: stacktrace[not captured])
[ 71.477] ERROR: Failed to allocate a large slot
[ 71.477] ERROR: Heap allocation error, layout = Layout {
size: 0x8000,
align: 8 (1 << 3),
}
It was first noticed in the CI Task "Test x86-64 / integration-test (syscall-debug, false, linux-efi-pe64) (push)" in commit 301fc47 in main, and then also appeared in PR #223. Re-running this task (once or a few times) makes it disappear.
@aneeshdurg Any thoughts on how it might happen?
There is a Heap Allocation Error of the following form that occurs in some recent CI runs:
It was first noticed in the CI Task "Test x86-64 / integration-test (syscall-debug, false, linux-efi-pe64) (push)" in commit 301fc47 in main, and then also appeared in PR #223. Re-running this task (once or a few times) makes it disappear.
@aneeshdurg Any thoughts on how it might happen?