The concurrency and switching tests take quite some time to finish (relatively speaking). When running in emulator and under a heavily loaded system (e.g. twister-ing), it may time out as the emulator is not getting much CPU time. So make the base timeout longer, which can then be further adjusted by the board timeout multiplier. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
40 lines
1.0 KiB
YAML
40 lines
1.0 KiB
YAML
common:
|
|
timeout: 300
|
|
tests:
|
|
kernel.multiprocessing.smp:
|
|
tags:
|
|
- kernel
|
|
- smp
|
|
ignore_faults: true
|
|
filter: (CONFIG_MP_MAX_NUM_CPUS > 1)
|
|
kernel.multiprocessing.smp.minimallibc:
|
|
tags:
|
|
- kernel
|
|
- smp
|
|
- libc
|
|
ignore_faults: true
|
|
filter: (CONFIG_MP_MAX_NUM_CPUS > 1) and CONFIG_MINIMAL_LIBC_SUPPORTED
|
|
extra_configs:
|
|
- CONFIG_MINIMAL_LIBC=y
|
|
kernel.multiprocessing.smp.affinity:
|
|
tags:
|
|
- kernel
|
|
- smp
|
|
ignore_faults: true
|
|
filter: (CONFIG_MP_MAX_NUM_CPUS > 1)
|
|
extra_configs:
|
|
- CONFIG_SCHED_CPU_MASK=y
|
|
|
|
kernel.multiprocessing.smp.affinity.custom_rom_offset:
|
|
tags:
|
|
- kernel
|
|
- smp
|
|
ignore_faults: true
|
|
filter: (CONFIG_MP_MAX_NUM_CPUS > 1)
|
|
platform_exclude:
|
|
- qemu_riscv64/qemu_virt_riscv64/smp # qemu_riscv64 doesn't support custom ROM offset
|
|
- qemu_riscv32/qemu_virt_riscv32/smp # qemu_riscv32 doesn't support custom ROM offset
|
|
extra_configs:
|
|
- CONFIG_SCHED_CPU_MASK=y
|
|
- CONFIG_ROM_START_OFFSET=0x80
|