Fix tests not passing on macOS with .NET Core 10

[Copilot]

Fixed the InMemoryJobLockProvider_ConcurrentAcquireAndRelease_ThreadSafe test that was failing on macOS with .NET 10.

Root Cause

The test used a 50ms TTL (time-to-live) for locks, but with 20 concurrent threads each holding the lock for 10ms, there was a race condition where locks could expire while threads still believed they held the lock. This was particularly problematic on macOS with .NET 10 due to different timing/scheduling behavior.

Changes Made

• Increased the TTL from TimeSpan.FromMilliseconds(50) to TimeSpan.FromSeconds(10) in the InMemoryJobLockProvider_ConcurrentAcquireAndRelease_ThreadSafe test
• Added explanatory comment to clarify why a long TTL is needed

This makes the test more robust across different platforms and .NET versions by ensuring locks don't expire during normal hold periods in the test.

Testing

• ✅ Test passes consistently (10 consecutive runs)
• ✅ All 17 InMemoryJobLockProvider tests pass
• ✅ Full test suite passes (155/155 tests)
• ✅ Code review: No issues
• ✅ Security scan: No alerts

The fix is minimal and surgical, addressing only the timing issue in the test without changing any production code.

Original prompt

Les tests ne passent pas sur macos avec la version 10 de .net core jai cette erreur aides moi :

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[jeanlrnt]

@copilot Continue

[Copilot]

@copilot Continue

Fixed in commit 2632d15. The issue was a race condition in the InMemoryJobLockProvider_ConcurrentAcquireAndRelease_ThreadSafe test where the 50ms TTL was too short, allowing locks to expire while threads still considered themselves to be holding the lock. Increased the TTL to 10 seconds to prevent this timing-sensitive issue on macOS with .NET 10. All 155 tests now pass.

[Copilot]

Pull request overview

This PR fixes a flaky test that was failing on macOS with .NET 10 due to a race condition caused by insufficient lock TTL (time-to-live). The test was using a 50ms TTL with 20 concurrent threads each holding locks for 10ms, causing locks to expire prematurely under certain timing/scheduling conditions specific to macOS and .NET 10.

• Increased the lock TTL from 50ms to 10 seconds in the InMemoryJobLockProvider_ConcurrentAcquireAndRelease_ThreadSafe test
• Added an explanatory comment to clarify the rationale for the longer TTL