CI

refactor: fix analyzer warnings (3) #2247

Sign in to view logs

GitHub Actions / Test Results failed Jan 12, 2025 in 0s

1 fail, 2 974 skipped, 52 217 pass in 21m 46s

46 files ±0 46 suites ±0 21m 46s ⏱️ -12s
55 192 tests - 6 52 217 ✅ - 6 2 974 💤 ±0 1 ❌ ±0
114 815 runs ±0 102 513 ✅ ±0 12 301 💤 ±0 1 ❌ ±0

Results for commit 40ddfe6. ± Comparison against earlier commit 5d24d73.

Annotations

Check warning on line 0 in Testably.Abstractions.Tests.TimeSystem.TimerTests.MockTimeSystemTests

github-actions / Test Results

1 out of 9 runs failed: Change_WithTimeSpan_ShouldResetTimer (Testably.Abstractions.Tests.TimeSystem.TimerTests.MockTimeSystemTests)

artifacts/Linux-artifacts/TestResults/Testably.Abstractions.Tests_net6.0.trx [took 0s]

Raw output


            Expected triggerTimes[i] to be greater than 1700, but found 0 (difference of -1700).   at FluentAssertions.Execution.XUnit2TestFramework.Throw(String message)
   at FluentAssertions.Execution.TestFrameworkProvider.Throw(String message)
   at FluentAssertions.Execution.DefaultAssertionStrategy.HandleFailure(String message)
   at FluentAssertions.Execution.AssertionScope.FailWith(Func`1 failReasonFunc)
   at FluentAssertions.Execution.AssertionScope.FailWith(Func`1 failReasonFunc)
   at FluentAssertions.Execution.AssertionScope.FailWith(String message, Object[] args)
   at FluentAssertions.Numeric.NumericAssertions`2.BeGreaterThan(T expected, String because, Object[] becauseArgs)
   at Testably.Abstractions.Tests.TimeSystem.TimerTests`1.Change_WithTimeSpan_ShouldResetTimer() in /home/runner/work/Testably.Abstractions/Testably.Abstractions/Tests/Testably.Abstractions.Tests/TimeSystem/TimerTests.cs:line 388

View more details on GitHub Actions