Repository navigation
Provision WSL and the test containers after the build instead of alongside it - #5873
Merged
Merged
Conversation
…ongside it Windows jobs have died with "The hosted runner lost communication with the server" while the build and the 8 GB WSL2 VM were competing for the runner's 16 GB. The WSL, SQL Server, PostgreSQL, RabbitMQ and IBM MQ setup steps now wait for the build like the Azure steps already did.
mauroservienti
approved these changes
Sep 9, 2026
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
2 participants
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.
Two Windows jobs in the last 60 CI runs (Windows-IBMMQ, 46 min; Windows-SqlServer on release-6.19, 52 min) ended with "The hosted runner lost communication with the server", GitHub's annotation for a runner starved of CPU or memory. Both were running the background build alongside the 8 GB WSL2 VM on a 16 GB runner.
The WSL, SQL Server, PostgreSQL, RabbitMQ and IBM MQ setup steps now sit behind
Wait for build, as the Azure steps already did. Costs those jobs the setup time that used to overlap the build, roughly a minute for WSL and up to three for SQL Server with full-text search.