Skip to content

Retry dotnet tool restore once on a cold-cache failure #86

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
Mpdreamz merged 1 commit into from
Sep 2, 2026
Merged

Retry dotnet tool restore once on a cold-cache failure #86

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
11 changes: 10 additions & 1 deletion build/scripts/Targets.fs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,16 @@ let private execResult binary args =
let result = Proc.Start(binary, List.toArray args)
result.ExitCode

let private restoreTools = lazy(exec "dotnet" ["tool"; "restore"])
/// dotnet/sdk#53783: on a cold tool-resolver cache (every fresh CI runner, every fresh container),
/// restoring 2+ RID-specific tool packages in one manifest can misattribute one package's
/// DotnetToolSettings.xml to another, failing with "The command ... is not contained in the
/// package ...". The cache is warm after the first attempt, so a bare retry always succeeds -
/// see https://github.com/dotnet/sdk/issues/53783.
let private restoreTools =
lazy(
try exec "dotnet" ["tool"; "restore"]
with _ -> exec "dotnet" ["tool"; "restore"]
)

let private currentVersion =
lazy(
Expand Down
Loading