CI

refactor: fix analyzer warnings #2224

Sign in to view logs

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

1 fail, 2 974 skipped, 52 219 pass in 22m 19s

46 files ±0 46 suites ±0 22m 19s ⏱️ +12s
55 194 tests ±0 52 219 ✅ - 1 2 974 💤 ±0 1 ❌ +1
114 806 runs ±0 102 504 ✅ - 1 12 301 💤 ±0 1 ❌ +1

Results for commit 2e914ba. ± Comparison against earlier commit f8f6426.

Annotations

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

github-actions / Test Results

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

artifacts/Linux-artifacts/TestResults/Testably.Abstractions.Tests_net8.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_WithInt_ShouldResetTimer() in /home/runner/work/Testably.Abstractions/Testably.Abstractions/Tests/Testably.Abstractions.Tests/TimeSystem/TimerTests.cs:line 236
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)

View more details on GitHub Actions