Skip to content

Conversation

@KGoreczny
Copy link

This job purpose is to run tests without using huge pages along the way. This limitation mimics mainly containerized environments - and in fact entire job could be run in container on the github runner without use of the qemu. For now run as any other job.
Currently only nvmf/tcp and some common autotest tests are suitable, this list can grow in future.

@KGoreczny KGoreczny marked this pull request as draft January 22, 2026 14:53
@KGoreczny KGoreczny force-pushed the nvmf-no-huge-vm-autotest branch 4 times, most recently from 01eb302 to 36c5830 Compare January 28, 2026 13:48
Krzysztof Goreczny added 2 commits January 28, 2026 10:38
Looking for just 'vm' to indicate if workflow is a VM or container based
fails if it happens that 'nvme' is also part of the workflow name.
For now assume that naming convention with '-vm-' and '-container-'
holds. Long term it might be better to rename and reuse
'cijoe_config_prefix' attribute or add one extra attribute.

Signed-off-by: Krzysztof Goreczny <krzysztof.goreczny@dell.com>
This job purpose is to run tests without using huge pages along the way.
This limitation mimics mainly containerized and/or development environments -
and in fact entire job runs in container on the github runner without
use of the QEMU.

Currently only nvmf/tcp and some common autotest tests are suitable, this
list can grow in future.

Signed-off-by: Krzysztof Goreczny <krzysztof.goreczny@dell.com>
@KGoreczny KGoreczny force-pushed the nvmf-no-huge-vm-autotest branch from 36c5830 to f99c1de Compare January 28, 2026 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant