Fix Infer ConfigureAwait test warnings #408
bitfaster
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
Annotations
11 warnings
|
infer:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L137
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
infer:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L264
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
infer:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L265
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
infer:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L274
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
infer:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L275
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
infer:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L296
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
infer:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L297
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
infer:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L137
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
infer:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L264
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
infer:
BitFaster.Caching.UnitTests/Lru/ConcurrentLruTests.cs#L265
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
|
infer
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|