Skip to content
BUILD

test: deactivate test UsesMultipleThreadsWhenConfigured because pipel… #149

Sign in to view logs

test: deactivate test UsesMultipleThreadsWhenConfigured because pipel…

test: deactivate test UsesMultipleThreadsWhenConfigured because pipel… #149

Triggered via push October 11, 2024 08:45
@VonDerBeckVonDerBeck
pushed c57d9bb
main
Status Success
Total duration 1m 21s
Artifacts –

build.yml

on: push
build
1m 12s
build
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
build: 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)
build: 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)
build: 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)
build: 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)
build: 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)
build: 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)