Skip to content

Commit 7b8941a

Browse files
smalis-msftmattkur
andauthored
CI: Tweak our nextest thread requirements (#2351)
Now that our requirements are in the right order, CI is taking significantly longer. Try scaling the requirements down a bunch. Co-authored-by: Matt LaFayette (Kurjanowicz) <[email protected]>
1 parent 87843b2 commit 7b8941a

File tree

1 file changed

+4
-7
lines changed

1 file changed

+4
-7
lines changed

.config/nextest.toml

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -28,23 +28,20 @@
2828
# same profile
2929
filter = 'package(~vmm_tests) and test(very_heavy)'
3030
# Mark very heavy tests as extra very heavy, as they include up to 32 vps.
31-
threads-required = 35
31+
# However most of these vps should spend most of their time idle.
32+
threads-required = 16
3233

3334
[[profile.default.overrides]]
3435
# use fuzzy-matching for the package() to allow out-of-tree tests to use the
3536
# same profile
3637
filter = 'package(~vmm_tests) and test(heavy) and not (test(very_heavy))'
3738
# Mark heavy tests as extra heavy, as they include up to 16 vps.
38-
threads-required = 18
39+
# However most of these vps should spend most of their time idle.
40+
threads-required = 8
3941

4042
[[profile.default.overrides]]
4143
# use fuzzy-matching for the package() to allow out-of-tree tests to use the
4244
# same profile
43-
filter = 'package(~vmm_tests) and test(openhcl)'
44-
# Mark OpenHCL VMM tests as extra heavy, as they have to also run VTL2.
45-
threads-required = 5
46-
47-
[[profile.default.overrides]]
4845
filter = 'package(~vmm_tests)'
4946
# Mark VMM tests as heavy and requiring more threads due to their memory and CPU
5047
# usage. For local dev runs, you may need to manually restrict the number of

0 commit comments

Comments
 (0)