Repository navigation
test(server): give slow service suites room on a busy host - #113
Merged
Merged
Conversation
github-actions
Bot
added
the
size:XS
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CI runs in a VM on the same Mac as other Vectis VMs. When the host is busy, the heaviest service suites (provision task, warm pool) exceed the 5 second test timeout or the 1 second
vi.waitFordefault, socheckfails at random: it failed on main after #109 and twice on #110/#111 with unrelated timeouts.A root Vitest config raises the test timeout to 15 seconds, and the polling waits in these two suites get 5 seconds. Passing tests are not slowed down.