ci: skip dotnet's first-time-experience setup in run_performance_tests - #411
Merged
twcclegg merged 1 commit intoAug 24, 2026
Merged
Conversation
Build both benchmark trees runs two dotnet build invocations concurrently via & - the only workflow that does, since everywhere else an earlier sequential dotnet restore/build step already completes the SDK's one-time setup (NuGet migrations, telemetry sentinel) before anything runs in parallel. Here the two concurrent invocations can race to perform that setup at once, both trying to create the same NuGet-Migrations mutex/ directory, and lose with "The system cannot open the device or file specified" / EEXIST - seen failing PR #409's run_performance_tests job. DOTNET_SKIP_FIRST_TIME_EXPERIENCE removes the race by skipping the setup entirely rather than reordering around it.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #411 +/- ##
=======================================
Coverage 77.26% 77.26%
=======================================
Files 39 39
Lines 4548 4548
Branches 1129 1129
=======================================
Hits 3514 3514
Misses 783 783
Partials 251 251 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
📊 Benchmark Results
PR branch
PR base
|
twcclegg
deleted the
ci/skip-dotnet-first-time-experience-in-perf-tests
branch
August 24, 2026 23:57
This was referenced Aug 28, 2026
Closed
Open
Merged
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
1 participant
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.
Summary
run_performance_tests.yml's "Build both benchmark trees" step runs twodotnet buildinvocations concurrently via&— the only workflow that does, since everywhere else an earlier sequentialdotnet restore/buildstep already completes the .NET SDK's one-time first-use setup (NuGet migrations, telemetry sentinel) before anything runs in parallel. Here, both concurrent invocations can race to perform that setup at once, both trying to create the sameNuGet-Migrationsmutex/directory, and one loses with:Seen failing PR #409's
run_performance_testscheck — unrelated to that PR's actual diff, purely this race.DOTNET_SKIP_FIRST_TIME_EXPERIENCE: true(plusDOTNET_NOLOGO: truefor consistency) removes the race by skipping the setup entirely rather than reordering around it.Test plan
dotnet buildinvocations, and none currently set these env vars