Skip to content

Code Refactoring

Code Refactoring #24

Triggered via push August 11, 2023 06:34
Status Success
Total duration 1m 47s
Artifacts

build.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

16 warnings
Build: tests/FileSystem.Tests/Base/UnitTestAdapter.cs#L75
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
Build: tests/FileSystem.Tests/Base/UnitTestAdapter.cs#L75
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build: tests/FileSystem.Tests/Base/IntegrationTestAdapter.cs#L84
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
Build: tests/FileSystem.Tests/Base/IntegrationTestAdapter.cs#L84
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build: tests/FileSystem.Tests/Base/UnitTestAdapter.cs#L75
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
Build: tests/FileSystem.Tests/Base/UnitTestAdapter.cs#L75
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build: tests/FileSystem.Tests/Base/IntegrationTestAdapter.cs#L84
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
Build: tests/FileSystem.Tests/Base/IntegrationTestAdapter.cs#L84
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Test: tests/FileSystem.Tests/Base/UnitTestAdapter.cs#L75
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
Test: tests/FileSystem.Tests/Base/UnitTestAdapter.cs#L75
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Test: tests/FileSystem.Tests/Base/IntegrationTestAdapter.cs#L84
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
Test: tests/FileSystem.Tests/Base/IntegrationTestAdapter.cs#L84
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Test: tests/FileSystem.Tests/Base/UnitTestAdapter.cs#L75
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
Test: tests/FileSystem.Tests/Base/UnitTestAdapter.cs#L75
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Test: tests/FileSystem.Tests/Base/IntegrationTestAdapter.cs#L84
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
Test: tests/FileSystem.Tests/Base/IntegrationTestAdapter.cs#L84
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.