zephyr/tests/lib/heap/testcase.yaml

# Excludes m2gl025_miv, which is based on the renode simulator.  This
# is very slow for CPU-bound tests like this, taking upwards of 10
# minutes (vs. ~20 seconds for qemu) to complete in CI.  There's
# little value there, this is a unit test of library code and we have
# coverage of the RISC-V architectures via qemu platforms already.
# Excludes qemu_xtensa due to pathological runtimes which cannot be
# reproduced on real hardware.
tests:
  lib.heap:
    tags: heap
    platform_exclude: m2gl025_miv qemu_xtensa
    filter: not CONFIG_SOC_NSIM
    timeout: 480
tests/lib/heap: Disable renode emulator platform The renode emulator is REALLY slow on this test, what completes in 20 seconds on qemu takes 4-10 minutes on renode. That's causing trouble in CI. And this is a CPU-bound unit test of library code, where we have coverage for riscv32 via qemu anyway. There's no value to having better platform emulation here. Signed-off-by: Andy Ross <andrew.j.ross@intel.com> 2020-04-09 23:35:59 +08:00			`# Excludes m2gl025_miv, which is based on the renode simulator. This`
			`# is very slow for CPU-bound tests like this, taking upwards of 10`
			`# minutes (vs. ~20 seconds for qemu) to complete in CI. There's`
			`# little value there, this is a unit test of library code and we have`
			`# coverage of the RISC-V architectures via qemu platforms already.`
tests: heap: exclude on qemu_xtensa This test takes a pathologically long time to run. The PR this is part of takes 10x as long to run the test as it did before. Such behavior cannot be reproduced on real Xtensa hardware, where the test completes on an Intel S1000 in 4 seconds. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com> 2020-09-23 10:20:36 +08:00			`# Excludes qemu_xtensa due to pathological runtimes which cannot be`
			`# reproduced on real hardware.`
tests/lib: Add sys_heap test Use the white box validation and test rig added as part of the sys_heap work. Add a layer that puts hashed cookies into the blocks to detect corruption, check the validity state after every operation, and enumerate a few different usage patterns: + Small heap, "real world" allocation where the heap is about half full and most allocations succeed. + Small heap, "fragmentation runaway" scenario where most allocations start failing, but the heap must remain consistent. + Big heap. We can't test this with the same exhaustive coverage (many re/allocations for every byte of storage) for performance reasons, but we do what we can. Signed-off-by: Andy Ross <andrew.j.ross@intel.com> 2019-07-18 01:31:24 +08:00			`tests:`
			`lib.heap:`
			`tags: heap`
tests: enable and run many tests on RISC-V This commit enables lots of tests on riscv32 and riscv64 which were previously disabled. Signed-off-by: Martin Åberg <martin.aberg@gaisler.com> 2021-01-08 04:16:03 +08:00			`platform_exclude: m2gl025_miv qemu_xtensa`
tests: filter out nsim as it's slow nsim is slow, if the MEMSZ is too targe, the test will run a long time and make sanitycheck timeout. There are two possible fixes to pass the sanitycheck test * filter out nsim, not to block the sanitcheck test * use a small MEMSZ for nsim to reduce the execution time. Considering there are potential improvements for nsim (because some qemu targets can pass), we use the 1st fix to pass the sanitycheck temporarily. Signed-off-by: Wayne Ren <wei.ren@synopsys.com> 2020-07-07 17:59:26 +08:00			`filter: not CONFIG_SOC_NSIM`
tests: enable and run many tests on RISC-V This commit enables lots of tests on riscv32 and riscv64 which were previously disabled. Signed-off-by: Martin Åberg <martin.aberg@gaisler.com> 2021-01-08 04:16:03 +08:00			`timeout: 480`