CI: serialize DB-dependent tests#2163
Merged
mgravell merged 2 commits intoDapperLib:mainfrom Apr 30, 2025
Merged
Conversation
mgravell
approved these changes
Apr 30, 2025
Member
|
CI is my personal nemesis. Appreciated. |
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.
Problem
Automated tests for the main branch are intermittently failing (though they sometimes succeed).
See: https://ci.appveyor.com/project/StackExchange/dapper
Example:
Cause
This is likely due to database-dependent tests being executed in parallel.
On December 22, 2024, AppVeyor updated their build image, which now includes the .NET 9 SDK:
https://www.appveyor.com/updates/2024/12/22/
Since Dapper targets multiple frameworks, this update caused tests to start running in parallel by default.
https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-test?tabs=dotnet-test-with-vstest#description-1
Solution
Following the official documentation, disable parallel execution of tests across TargetFrameworks.