Skip to content

fix: Use explicit solution file in DotNetTests to prevent flaky failures #1682

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
thomhurst merged 1 commit into from
Dec 30, 2025
Merged

fix: Use explicit solution file in DotNetTests to prevent flaky failures #1682

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
4 changes: 3 additions & 1 deletion test/ModularPipelines.UnitTests/Helpers/DotNetTests.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,11 @@ private class DotNetVersionModule : Module<CommandResult>
{
public override async Task<CommandResult?> ExecuteAsync(IModuleContext context, CancellationToken cancellationToken)
{
// Use main solution explicitly - FindFile returns first match alphabetically
// which could be ModularPipelines.Analyzers.sln causing flaky failures
return await context.DotNet().List.Package(new DotNetListPackageOptions
{
ProjectSolution = context.Git().RootDirectory.FindFile(x => x.Extension == ".sln").AssertExists(),
ProjectSolution = context.Git().RootDirectory.FindFile(x => x.Name == "ModularPipelines.sln").AssertExists(),
}, token: cancellationToken);
}
}
Expand Down
Loading