Skip to content

ANALYZE

ANALYZE #205

Triggered via schedule November 8, 2024 09:29
Status Success
Total duration 2m 21s
Artifacts

analyze.yml

on: schedule
Matrix: Analyze
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Analyze (csharp): test/Zeebe.Client.Accelerator.Integration.Tests/Test.cs#L135
Public method 'UsesMultipleThreadsWhenConfigured' on test class 'Test' should be marked as a Fact. Reduce the visibility of the method, or add a Fact attribute to the method. (https://xunit.net/xunit.analyzers/rules/xUnit1013)
Analyze (csharp): test/Zeebe.Client.Accelerator.Unit.Tests/ZeebeHostedServiceTests.cs#L158
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
Analyze (csharp): test/Zeebe.Client.Accelerator.Unit.Tests/ZeebeHostedServiceTests.cs#L189
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
Analyze (csharp): test/Zeebe.Client.Accelerator.Integration.Tests/Test.cs#L135
Public method 'UsesMultipleThreadsWhenConfigured' on test class 'Test' should be marked as a Fact. Reduce the visibility of the method, or add a Fact attribute to the method. (https://xunit.net/xunit.analyzers/rules/xUnit1013)
Analyze (csharp): test/Zeebe.Client.Accelerator.Unit.Tests/ZeebeHostedServiceTests.cs#L158
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
Analyze (csharp): test/Zeebe.Client.Accelerator.Unit.Tests/ZeebeHostedServiceTests.cs#L189
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)