Fix flaky Kill_Test on macOS by waiting for process exit before asserting

[Copilot]

ProcessTests.Kill_Test was intermittently failing on macOS because Process.Kill() sends SIGKILL and returns before the OS reaps the process — making HasExited transiently false.

Change

Added process.WaitForExit() between the Kill(true) call and the HasExited assertion, ensuring the process is fully terminated before the check:

// Act
process.Kill(true);
process.WaitForExit(); // ← added

// Assert
process.HasExited.Should().BeTrue();

[Copilot]

Pull request overview

Fixes an intermittent macOS test failure in ProcessTests.Kill_Test by ensuring the killed process has fully exited before asserting HasExited, aligning the test with how Process.Kill() can return before the OS reaps the process.

Changes:

• Added process.WaitForExit() after process.Kill(true) in Kill_Test to reduce flakiness on macOS.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.82%. Comparing base (0cd6e1d) to head (ba9b6ec).
⚠️ Report is 1 commits behind head on prime.

Additional details and impacted files

@@            Coverage Diff             @@
##            prime     #117      +/-   ##
==========================================
+ Coverage   90.77%   90.82%   +0.04%     
==========================================
  Files         284      284              
  Lines        4934     4935       +1     
  Branches      404      404              
==========================================
+ Hits         4479     4482       +3     
+ Misses        365      363       -2     
  Partials       90       90              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Tyrrrz]

@copilot build/test failing

[Copilot]

@copilot build/test failing

Fixed in 3b8c712. The WaitForExit(TimeSpan) overload is only available on .NET 7+, which caused the build failure on net6.0. Switched to WaitForExit(int milliseconds) which is available on all target frameworks.

[Tyrrrz]

@copilot I've added the TimeSpan polyfill in the latest prime. Please update and revert last change. Also update the test's arrange phase so that it's consistent with the other similar tests, such as those added in the last commit to prime.