Skip to content

feat: use monotonic clock for PeriodicTimer and Stopwatch #987

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
vbreuss merged 2 commits into from
Apr 6, 2026

Fix review issues

b0703b2
Select commit
Loading
Failed to load commit list.
Sign in for the full log view
Merged

feat: use monotonic clock for PeriodicTimer and Stopwatch #987

Fix review issues
b0703b2
Select commit
Loading
Failed to load commit list.
GitHub Actions / Test Results failed Apr 6, 2026 in 0s

1 fail, 12 610 skipped, 99 853 pass in 2h 30m 2s

    102 files  +    102      102 suites  +102   2h 30m 2s ⏱️ + 2h 30m 2s
112 464 tests +112 464   99 853 ✅ + 99 853  12 610 💤 +12 610  1 ❌ +1 
268 200 runs  +268 200  231 511 ✅ +231 511  36 688 💤 +36 688  1 ❌ +1 

Results for commit b0703b2. ± Comparison against earlier commit dc30fa8.

Annotations

Check warning on line 0 in Testably.Abstractions.Tests.TimeSystem.StopwatchTests

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 40 runs failed: Stop_ShouldSetIsRunningToFalse (Testably.Abstractions.Tests.TimeSystem.StopwatchTests) 

artifacts/Windows-artifacts/TestResults/runneradmin_runnervmsit9q_2026-04-06_15_25_46.9547713.trx [took 0s]
Raw output 
FailException: Expected that elapsed.TotalMilliseconds
is greater than or equal to 99.0,
but it was 98.9479   at aweXpect.Results.ExpectationResult`2.GetResultOrThrow()
   at Testably.Abstractions.Tests.TimeSystem.StopwatchTests.Stop_ShouldSetIsRunningToFalse() in D:\a\Testably.Abstractions\Testably.Abstractions\Tests\Testably.Abstractions.Tests\TimeSystem\StopwatchTests.cs:line 141
View more details on GitHub Actions