Skip to content

CI: Give vmm tests more threads and more time #2145

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
smalis-msft merged 1 commit into from
Oct 11, 2025
Merged

CI: Give vmm tests more threads and more time #2145

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions .config/nextest.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,21 +6,21 @@ filter = 'package(~vmm_tests)'
# Mark VMM tests as heavy and requiring more threads due to their memory and CPU
# usage. For local dev runs, you may need to manually restrict the number of
# threads running via the -j cli arg.
threads-required = 2
threads-required = 3

[[profile.default.overrides]]
# use fuzzy-matching for the package() to allow out-of-tree tests to use the
# same profile
filter = 'package(~vmm_tests) and test(openhcl)'
# Mark OpenHCL VMM tests as extra heavy, as they have to also simulate VTL2.
threads-required = 4
# Mark OpenHCL VMM tests as extra heavy, as they have to also run VTL2.
threads-required = 6

[[profile.default.overrides]]
# use fuzzy-matching for the package() to allow out-of-tree tests to use the
# same profile
filter = 'package(~vmm_tests) and test(heavy)'
# Mark heavy tests as extra heavy, as they include up to 16 vps.
threads-required = 16
threads-required = 24

# Profile for CI runs.
[profile.ci]
Expand All @@ -46,4 +46,4 @@ slow-timeout = { period = "30s", terminate-after = 2 }
filter = 'package(~vmm_tests)'
# VMM tests contain their own watchdog timer, but keep an extra long timer
# here as a backup.
slow-timeout = { period = "10m", terminate-after = 1 }
slow-timeout = { period = "15m", terminate-after = 1 }
2 changes: 1 addition & 1 deletion petri/src/vm/mod.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -323,7 +323,7 @@ impl<T: PetriVmmBackend> PetriVmBuilder<T> {
let mut tasks = Vec::new();

{
const TIMEOUT_DURATION_MINUTES: u64 = 7;
const TIMEOUT_DURATION_MINUTES: u64 = 10;
const TIMER_DURATION: Duration = Duration::from_secs(TIMEOUT_DURATION_MINUTES * 60);
let log_source = resources.log_source.clone();
let inspect_task =
Expand Down
4 changes: 2 additions & 2 deletions vmm_tests/vmm_tests/tests/tests/multiarch.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -521,7 +521,7 @@ async fn memory_validation_cvm_small<T: PetriVmmBackend>(
hyperv_openhcl_uefi_aarch64(vhd(ubuntu_2404_server_aarch64))
)]
#[cfg_attr(not(windows), expect(dead_code))]
async fn memory_validation_gp_large<T: PetriVmmBackend>(
async fn memory_validation_gp_heavy<T: PetriVmmBackend>(
config: PetriVmBuilder<T>,
_: (),
driver: pal_async::DefaultDriver,
Expand All @@ -543,7 +543,7 @@ async fn memory_validation_gp_large<T: PetriVmmBackend>(
hyperv_openhcl_uefi_x64[snp](vhd(windows_datacenter_core_2025_x64_prepped)),
)]
#[cfg_attr(not(windows), expect(dead_code))]
async fn memory_validation_cvm_large<T: PetriVmmBackend>(
async fn memory_validation_cvm_heavy<T: PetriVmmBackend>(
config: PetriVmBuilder<T>,
_: (),
driver: pal_async::DefaultDriver,
Expand Down