Skip to content

Filter out progress indicators from command-line output (fix #2954) #807

Filter out progress indicators from command-line output (fix #2954)

Filter out progress indicators from command-line output (fix #2954) #807

Triggered via push November 14, 2024 18:16
Status Success
Total duration 3m 14s
Artifacts

dotnet-test.yml

on: push
test-codebase
3m 0s
test-codebase
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
test-codebase: src/UniGetUI.Core.Classes/TaskRecycler.cs#L147
Member 'DeduplicatedCalls' is explicitly initialized to its default value (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1805)
test-codebase: src/UniGetUI.Core.Classes.Tests/TaskRecyclerTests.cs#L40
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)
test-codebase: src/UniGetUI.Core.Classes.Tests/TaskRecyclerTests.cs#L41
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)
test-codebase: src/UniGetUI.Core.Classes.Tests/TaskRecyclerTests.cs#L47
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)
test-codebase: src/UniGetUI.Core.Classes.Tests/TaskRecyclerTests.cs#L48
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)
test-codebase: src/UniGetUI.Core.Classes.Tests/TaskRecyclerTests.cs#L61
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)
test-codebase: src/UniGetUI.Core.Classes.Tests/TaskRecyclerTests.cs#L62
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)
test-codebase: src/UniGetUI.Core.Classes.Tests/TaskRecyclerTests.cs#L69
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)
test-codebase: src/UniGetUI.Core.Classes.Tests/TaskRecyclerTests.cs#L70
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)
test-codebase: src/UniGetUI.Core.Classes.Tests/TaskRecyclerTests.cs#L80
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)