Fix Infer ConfigureAwait test warnings #1205
bitfaster
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
Annotations
4 errors and 21 warnings
|
mac
Process completed with exit code 1.
|
|
mac
Failed tests were found and 'fail-on-error' option is set to true
|
|
win
Failed tests were found and 'fail-on-error' option is set to true
|
|
win
Process completed with exit code 1.
|
|
mac:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L137
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
|
mac:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L264
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
|
mac:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L265
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
|
mac:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L274
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
|
mac:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L275
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
|
mac:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L296
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
|
mac:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L297
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
|
mac:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L137
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
|
mac:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L274
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
|
mac:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L275
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
|
win:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L137
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
win:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L264
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
win:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L265
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
win:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L274
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
win:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L275
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
win:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L296
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
win:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L297
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
win:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L137
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
win:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L264
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
win:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L265
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
win
.NET Core 3.1 is no longer supported and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the .NET support policy.
|