Skip to content

ConcurrentLfu.Clear() polluted by removed items #406

ConcurrentLfu.Clear() polluted by removed items

ConcurrentLfu.Clear() polluted by removed items #406

Triggered via pull request October 2, 2023 18:23
Status Success
Total duration 1m 17s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

infer.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
infer: BitFaster.Caching.UnitTests/Lfu/ConcurrentLfuTests.cs#L69
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
infer: BitFaster.Caching.UnitTests/Lfu/ConcurrentLfuTests.cs#L70
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
infer: BitFaster.Caching.UnitTests/Lfu/ConcurrentLfuTests.cs#L59
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
infer: BitFaster.Caching.UnitTests/Lfu/ConcurrentLfuTests.cs#L60
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
infer: BitFaster.Caching.UnitTests/Lru/ClassicLruTests.cs#L198
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
infer: BitFaster.Caching.UnitTests/Lru/ClassicLruTests.cs#L199
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/ClassicLruTests.cs#L208
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
infer: BitFaster.Caching.UnitTests/Lru/ClassicLruTests.cs#L209
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
infer: BitFaster.Caching.UnitTests/Lru/ClassicLruTests.cs#L230
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/