Skip to content

[main] Bump System.Management from 9.0.4 to 10.0.12 - #11140

Merged
Amaury Levé (Evangelink) merged 4 commits into
mainfrom
dependabot/nuget/System.Management-10.0.12
Sep 10, 2026
Merged

Amaury Levé (Evangelink) merged 4 commits into
mainfrom
dependabot/nuget/System.Management-10.0.12

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 9, 2026

Copy link
Copy Markdown
Contributor

Updated System.Management from 9.0.4 to 10.0.12.

Release notes

Sourced from System.Management's releases.

10.0.12

Release

What's Changed

... (truncated)

10.0.0-preview.6.25358.103

You can build .NET 10.0 Preview 6 from the repository by cloning the release tag v10.0.0-preview.6.25358.103 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.5.25277.114

You can build .NET 10.0 Preview 5 from the repository by cloning the release tag v10.0.0-preview.5.25277.114 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.4.25258.110

You can build .NET 10.0 Preview 4 from the repository by cloning the release tag v10.0.0-preview.4.25258.110 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.3.25171.5

You can build .NET 10.0 Preview 3 from the repository by cloning the release tag v10.0.0-preview.3.25171.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.2.25163.2

You can build .NET 10.0 Preview 2 from the repository by cloning the release tag v10.0.0-preview.2.25163.2 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.1.25080.5

You can build .NET 10.0 Preview 1 from the repository by cloning the release tag v10.0.0-preview.1.25080.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.121

You can build .NET 9.0 from the repository by cloning the release tag v9.0.121 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.120

You can build .NET 9.0 from the repository by cloning the release tag v9.0.120 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is a PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.119

You can build .NET 9.0 from the repository by cloning the release tag v9.0.119 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.118

You can build .NET 9.0 from the repository by cloning the release tag v9.0.118 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is a PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.117

You can build .NET 9.0 from the repository by cloning the release tag v9.0.117 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.116

You can build .NET 9.0 from the repository by cloning the release tag v9.0.116 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.115

You can build .NET 9.0 from the repository by cloning the release tag v9.0.115 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.114

You can build .NET 9.0 from the repository by cloning the release tag v9.0.114 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is the PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.113

You can build .NET 9.0 from the repository by cloning the release tag v9.0.113 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.112

You can build .NET 9.0 from the repository by cloning the release tag v9.0.112 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.111

You can build .NET 9.0 from the repository by cloning the release tag v9.0.111 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.110

You can build .NET 9.0 from the repository by cloning the release tag v9.0.110 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.109

You can build .NET 9.0 from the repository by cloning the release tag v9.0.109 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.101

You can build .NET 9.0 from the repository by cloning the release tag v9.0.101 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.7

You can build .NET 9.0 from the repository by cloning the release tag v9.0.7 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.6

You can build .NET 9.0 from the repository by cloning the release tag v9.0.6 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.5

You can build .NET 9.0 from the repository by cloning the release tag v9.0.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

Commits viewable in compare view.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---
updated-dependencies:
- dependency-name: System.Management
  dependency-version: 10.0.12
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Updates to dependency manifests. label Sep 9, 2026
Copilot AI balanced review requested due to automatic review settings September 9, 2026 07:13
@dependabot dependabot Bot added the dependencies Updates to dependency manifests. label Sep 9, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The focused dependency update is consistent with central package management and its usage remains compatible.

Pull request overview

Updates the centrally managed System.Management dependency for the performance runner from 9.0.4 to 10.0.12.

Changes:

  • Bumps System.Management to version 10.0.12.
File summaries
File Description
Directory.Packages.props Updates the central package version.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Balanced

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

Limit the idle-client disposal test to verifying that disposal completes. Linux may surface the forced close as a connection reset rather than EOF.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings September 9, 2026 15:13
@github-actions

This comment has been minimized.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The unrelated test edit removes meaningful disconnect coverage and should be restored.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details
  • Files reviewed: 2/2 changed files
  • Comments generated: 1
  • Review effort level: Balanced

@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

🧪 Expert test review — PR #11140

This PR is nominally a dependency bump (System.Management 9.0.4 → 10.0.12) but also carries an unrelated test change in TestHostControllerCancellationTests.cs that weakens one existing test's assertions. Only one test method falls in the changed lines.

GradeTestMutationNotesHow to improve
B (80–89) mod TestHostControllerCancellationTests.
ServerDisposal_
WhenClientConnectsWithoutSendingRequest_
DoesNotHang
2/3 killed Now only verifies Dispose returns within timeout; the removed read/assert was the only check that the client's pipe is actually disconnected, so a regression that disposes without closing this pre-request connection would no longer be caught (the analogous post-request test still checks this). Restore the disconnect read and assert 0 bytes, wrapped in a try/catch for the platform-dependent IOException (connection reset) that Linux can surface instead of EOF — mirroring the fix already applied to ServerDisposal_WhenClientKeepsConnectionOpenAfterRequest_DoesNotHang.

Summary: The commit message claims this narrows the test to avoid Linux flakiness (EOF vs. connection-reset), but the applied fix is a straight deletion rather than tolerating both outcomes as the sibling test (ServerDisposal_WhenClientKeepsConnectionOpenAfterRequest_DoesNotHang, lines ~145–153) already does — that test still reads until disconnect and asserts 0 bytes. Deleting the check here instead of hardening it removes real mutation coverage: a regression where Dispose() returns but leaves the pre-request pipe open would now pass silently. Posted one inline suggestion restoring the check with an IOException catch to make it robust on Linux while keeping the original intent.

This advisory comment was generated automatically. Grades are heuristic
and informational — they do not block merging. Suggestions on the Files
changed tab can be applied with one click. Re-run with
/review-tests.

🤖 Automated content by GitHub Copilot. Generated by the Test Reviewer on PR (on open / sync) workflow. · auto · 189.9 AIC · ⌖ 2.49 AIC · ⊞ 15.9K · [◷]( · ◷)

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Automated content by GitHub Copilot. Generated by the Test Reviewer on PR (on open / sync) workflow. · auto · 189.9 AIC · ⌖ 2.49 AIC · ⊞ 15.9K · ◷

@github-actions

This comment has been minimized.

Bound the client read and accept the Linux connection-reset result while preserving the EOF assertion on graceful disconnects.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings September 10, 2026 08:14

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The dependency update is focused, and the revised test preserves its disconnect assertion while handling platform-specific behavior.

Review details
  • Files reviewed: 2/2 changed files
  • Comments generated: 0 new
  • Review effort level: Balanced

@github-actions

This comment has been minimized.

@github-actions

Copy link
Copy Markdown
Contributor

🧪 Expert test review — PR #11140

GradeTestMutationNotesHow to improve
A (90–100) mod TestHostControllerCancellationTests.
ServerDisposal_
WhenClientConnectsWithoutSendingRequest_
DoesNotHang
2/2 killed Restored disconnect assertion is bounded with Task.WhenAny and narrowly tolerates only Unix's SocketError.ConnectionReset instead of swallowing all IOExceptions. —

Only one test method's body actually changed in this PR (Directory.Packages.props is a dependency bump, unrelated to tests). The prior review round (see resolved threads) correctly flagged that an earlier revision had dropped the disconnect check entirely; commit 530f21492 restored it properly: the read is now raced against a Task.Delay(DisposalTestTimeout) so a regression that leaves the pipe open causes a real, bounded assertion failure (AreSame) instead of an indefinite hang, AreEqual(0, bytesRead) still confirms a graceful EOF close, and the catch clause is scoped to the specific SocketException.SocketErrorCode == ConnectionReset case rather than a bare catch (IOException), so it won't mask unrelated I/O failures. No further action needed.

This advisory comment was generated automatically. Grades are heuristic
and informational — they do not block merging. Suggestions on the Files
changed tab can be applied with one click. Re-run with
/review-tests.

🤖 Automated content by GitHub Copilot. Generated by the Test Reviewer on PR (on open / sync) workflow. · auto · 72.4 AIC · ⌖ 2.39 AIC · ⊞ 15.9K · [◷]( · ◷)

@github-actions

Copy link
Copy Markdown
Contributor

Pipeline Test Triage — Final Resolution

Status: Final (completed build analysis)

Build: [1590514]((dev.azure.com/redacted) (microsoft.testfx), branch refs/pull/11140/merge

Affected leg: Windows Release only (net10.0). Linux Release and other legs were unaffected.

Failure signature

  • Test: Microsoft.Testing.Platform.Acceptance.IntegrationTests.TrxTests.Trx_CommandLineOptionDefault_IsPassiveAndExplicitValueWins("net10.0")
  • Error: System.IO.IOException: The process cannot access the file '...\TrxTest\bin\Release\net10.0\TestResults\trx-stream-*.bin' because it is being used by another process.
  • Location: TempDirectory.CopyDirectoryAsync (test infrastructure helper used by AcceptanceTestBase.CloneTestHostAsync), not product code under test.
  • No CTRF retry attempts were recorded for this run (retryAttempts: []), so this is a single, non-retried failure — no fail‐then‐pass evidence, so it does not meet the "flaky" bar, only "single occurrence."

Historical context

Checked the 3 most recent completed builds with a matching test record (1590480, 1590355, 1590337): this test passed in all of them (CTRF and JUnit both passed). No prior occurrence of this exact IOException signature was found in the bounded 30-day/12-build history window, and no matching open or closed GitHub issue was found for this signature (searched for trx-stream, CopyDirectoryAsync, and the test name).

Assessment

This looks like a transient Windows file-locking race during test-cleanup (copying the test host output directory while the TRX stream writer still has trx-stream-*.bin open), not a defect introduced by this PR. The PR itself (System.Management dependency bump) has no plausible connection to TRX streaming or TempDirectory cleanup. With only one occurrence and no historical recurrence, this does not meet the durable-issue threshold (would need a second independent build/commit showing the same signature, or high-confidence deterministic regression evidence — neither is present here).

Conclusion: Environmental one-off failure. No issue created. Recommend re-running the Windows Release leg; if this signature recurs on unrelated commits, escalate to an issue citing this build for context.

🤖 Automated content by GitHub Copilot. Generated by the Pipeline Test Triage workflow. · auto · 79.1 AIC · ⌖ 2.41 AIC · ⊞ 8.9K · [◷]( · ◷)

Prevent test methods from cloning and executing the shared mutable TRX asset concurrently, which can lock the streaming sidecar on Windows.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings September 10, 2026 12:50

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The package exists, supports the consuming target framework, and the accompanying test stabilizations are sound.

Review details
  • Files reviewed: 3/3 changed files
  • Comments generated: 0 new
  • Review effort level: Balanced

@github-actions

Copy link
Copy Markdown
Contributor

🧪 Expert test review — PR #11140

GradeTestMutationNotesHow to improve
A (90–100) mod TestHostControllerCancellationTests.
ServerDisposal_
WhenClientConnectsWithoutSendingRequest_
DoesNotHang
2/2 killed Checks the read completed (not timed out) via AreSame then asserts EOF, with a narrowly-scoped Linux reset fallback. —

Only one changed test file in this PR contains a modified test method (TestHostControllerCancellationTests.ServerDisposal_WhenClientConnectsWithoutSendingRequest_DoesNotHang); the TrxTests.cs change only adds a [DoNotParallelize] class attribute and touches no test method bodies. The Directory.Packages.props change is a dependency bump with no test content.

The reviewed change restores the disconnect assertion (Assert.AreEqual(0, bytesRead)) that a prior revision had dropped — flagged and fixed per the existing review thread on this PR — and additionally guards against the read hanging by racing it against a timeout (Task.WhenAny + Assert.AreSame), while tolerating the platform-specific SocketError.ConnectionReset some CI legs observe on Linux instead of a graceful EOF. No further high-confidence issues found; no inline suggestions posted.

This advisory comment was generated automatically. Grades are heuristic
and informational — they do not block merging. Suggestions on the Files
changed tab can be applied with one click. Re-run with
/review-tests.

🤖 Automated content by GitHub Copilot. Generated by the Test Reviewer on PR (on open / sync) workflow. · auto · 172 AIC · ⌖ 2.41 AIC · ⊞ 15.9K · [◷]( · ◷)

@github-actions

Copy link
Copy Markdown
Contributor

🧵 Parallel-safety audit — PR #11140

Parallelization — assemblies touched by this PR:

Test assembly Scope Workers Analyzer coverage
Microsoft.Testing.Platform.Acceptance.IntegrationTests MethodLevel 0 (CPU count) coverable once the parallel-safety analyzers ship (assembly attribute in Program.cs)
Microsoft.Testing.Platform.UnitTests MethodLevel 0 (CPU count) coverable once the parallel-safety analyzers ship (assembly attribute in Program.cs)

Both assemblies opt in via [assembly: Parallelize(Scope = ExecutionScope.MethodLevel, Workers = 0)] only — no .runsettings/testconfig.json override was found, so once MSTEST0074–0077 ship they will see these suites. No parallelization-state files were touched by this PR (only Directory.Packages.props, TrxTests.cs, TestHostControllerCancellationTests.cs changed).

Findings: A (global-state) 0 · B (paths) 0 · C (declaration) 1 · D (over-serialization) 1 — by severity: Critical 0 · High 0 · Warning 0 · Info 2.

Top actions (by expected value):

  1. No action required — the PR's only parallel-safety-relevant change (adding class-level [DoNotParallelize] to TrxTests) is a net-positive fix for a genuine shared-asset race and matches existing sibling-class convention.
  2. Optionally revisit TrxTests's serialization granularity later if this class becomes a build-time bottleneck (see Info finding below) — not urgent.

Info

  • [C/D · Medium confidence] test/IntegrationTests/Microsoft.Testing.Platform.Acceptance.IntegrationTests/TrxTests.cs:9 — this PR adds class-level [DoNotParallelize] on top of the existing [TestClass]. Under this assembly's MethodLevel scope, this is a correct fix: several methods in the class (e.g. Trx_WhenReportTrxIsNotSpecified_TrxReportIsNotGenerated, Trx_WhenReportTrxIsSpecified_TrxReportIsGeneratedInDefaultLocation, Trx_WhenOnlyReportTrxIsSpecified_UsesControllerBackedRecoveryByDefault, Trx_WhenTestHostCrash_ErrorIsDisplayedInsideTheTrx, Trx_WhenReportTrxIsSpecifiedWithRelativePath_TrxReportIsGeneratedUnderResultsDirectory, Trx_WhenReportTrxIsSpecifiedAndReportTrxPathIsSpecified_Overwritten) write TRX/artifact output into testHost.DirectoryName or the shared default bin/Release/<tfm>/TestResults location without a per-test-unique subdirectory, and all methods in the class share the same underlying built asset (AssetFixture.TargetAssetPath + TestAssetFixture.AssetName, one build per tfm) — a genuine cross-method collision under MethodLevel that was previously undeclared (latent race, matches the commit message: "shared mutable TRX asset... can lock the streaming sidecar on Windows"). This mirrors the same pattern already used in sibling fixtures in this project (CtrfReportTests, HtmlReportTests, PackagedWinUITests, PackagedAppDeploymentTests), all of which use class-level [DoNotParallelize] for the same "shared build asset" reason, so this is a deliberate, consistent codebase convention rather than a one-off. Fix (optional, not required): none needed now; if this class's wall-clock time becomes a bottleneck, note that several other methods (e.g. Trx_WhenOutOfProcessReportHasNoSelectedTests_LifetimeHandshakeCompletes:108, Trx_WhenReportTrxAndResultsDirectoryAreSpecifiedWithArtifact_ArtifactIsCopiedUnderRelativeResultsDirectory:134, Trx_WhenArtifactDestinationExceedsWindowsMaxPath_ArtifactIsStillCopied:181, Trx_WhenPerTestArtifactCannotBeCopied_WarningIsSurfacedAndResultFileIsSkipped:212, Trx_WhenTimeoutTerminatesTestHost_RecoversCompletedResults:265, Trx_WhenTestHostCrash_RunningUnderDotnetTest_ErrorIsDisplayedInsideTheTrx:295, Trx_WhenReportTrxIsSpecifiedWithFullPath_TrxReportIsGeneratedAtThatPath:317) already write to a Guid.NewGuid()-based unique results directory and don't collide with anything, so a narrower [ResourceLock] limited to the conflicting subset could recover some concurrency there — unquantified, since acceptance test wall time here is dominated by process/build spawn cost rather than lock contention.
  • [readiness · High confidence] test/UnitTests/Microsoft.Testing.Platform.UnitTests/Hosts/TestHostControllerCancellationTests.cs:78-108 — the changed test body (ServerDisposal_WhenClientConnectsWithoutSendingRequest_DoesNotHang) uses a per-instance Guid.NewGuid()-based pipe name (TestHostControllerCancellationServer constructor, CONTROLTOHOST_{Guid.NewGuid():N}) and a fresh, locally-scoped NamedPipeClientStream/mock — no process-global state (env vars, CWD, console, shared paths, static fields) is touched, so there is no parallel-safety concern here. This is a flakiness/robustness fix (retry-tolerant socket-exception handling), out of scope for this audit — see test-anti-patterns for that angle.

Advisory only — heuristic, non-blocking. Re-run with /parallel-audit. This audit answers "is it parallel-safe?"; for testability, smells, or flakiness see the detect-static-dependencies / test-smell-detection / test-anti-patterns analyses.

🤖 Automated content by GitHub Copilot. Generated by the Parallel-safety audit on PR (on open / sync) workflow. · auto · 149.7 AIC · ⌖ 3.37 AIC · ⊞ 23.9K · [◷]( · ◷)

@Evangelink
Amaury Levé (Evangelink) merged commit 9ad2651 into main Sep 10, 2026
30 checks passed
@Evangelink
Amaury Levé (Evangelink) deleted the dependabot/nuget/System.Management-10.0.12 branch September 10, 2026 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Updates to dependency manifests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants