refactor: use aweXpect for Compression project #2131
Annotations
1 error and 14 warnings
|
Run tests
Process returned exit code 1
Launched as "pwsh -command ". 'D:\a\_actions\Wandalen\wretry.action\v3.7.3_js_action\src\script.ps1'""
Launched at "/D/a/Testably.Abstractions/Testably.Abstractions"
Attempts exhausted, made 2 attempts :
Attempt #1 started at : 15:37:23 GMT+0000 (Coordinated Universal Time)
Attempt #2 started at : 15:46:09 GMT+0000 (Coordinated Universal Time)
|
|
Pre Run tests
Environment variable 'INPUT_GITHUB_CONTEXT' exceeds the maximum supported length. Environment variable length: 35037 , Maximum supported length: 32766
|
|
Run tests
Environment variable 'INPUT_GITHUB_CONTEXT' exceeds the maximum supported length. Environment variable length: 35037 , Maximum supported length: 32766
|
|
Post Run tests
Environment variable 'INPUT_GITHUB_CONTEXT' exceeds the maximum supported length. Environment variable length: 35037 , Maximum supported length: 32766
|
|
Build solution:
Tests/Testably.Abstractions.Compression.Tests/ZipFile/Tests.cs#L9
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 solution:
Tests/Testably.Abstractions.Compression.Tests/ZipFile/OpenTests.cs#L11
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 solution:
Tests/Testably.Abstractions.Compression.Tests/ZipFile/OpenTests.cs#L19
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 solution:
Tests/Testably.Abstractions.Compression.Tests/ZipFile/OpenTests.cs#L35
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 solution:
Tests/Testably.Abstractions.Compression.Tests/ZipFile/OpenTests.cs#L51
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 solution:
Tests/Testably.Abstractions.Compression.Tests/ZipFile/ExtractToDirectoryTests.cs#L16
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 solution:
Tests/Testably.Abstractions.Compression.Tests/ZipFile/ExtractToDirectoryTests.cs#L35
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 solution:
Tests/Testably.Abstractions.Compression.Tests/ZipFile/ExtractToDirectoryTests.cs#L52
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 solution:
Tests/Testably.Abstractions.Compression.Tests/ZipFile/ExtractToDirectoryTests.cs#L69
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 solution:
Tests/Testably.Abstractions.Compression.Tests/ZipFile/ExtractToDirectoryTests.cs#L94
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.
|
|
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "Code coverage (.NET Framework)", "PR_NUMBER", "Stryker", "Test results (.NET Framework)", "Test results (MacOS)", "Test results (Ubuntu)", "Test results (Windows)".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Loading