Crossbow #203227
Annotations
1 error and 11 warnings
Run verification
Process completed with exit code 3.
|
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Run verification
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Run verification
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Run verification
Adding a finalizer to a type derived from MemoryManager<T> may permit memory to be freed while it is still in use by a Span<T>
|
Run verification
Do not use Assert.Equal() to check for collection size. Use Assert.Single instead.
|
Run verification
Nullability of type of parameter 'value' doesn't match overridden member (possibly because of nullability attributes).
|
Run verification
Test methods should not call ConfigureAwait(false), as it may bypass parallelization limits. Omit ConfigureAwait, or use ConfigureAwait(true) to avoid CA2007.
|
Run verification
Test methods should not call ConfigureAwait(false), as it may bypass parallelization limits. Omit ConfigureAwait, or use ConfigureAwait(true) to avoid CA2007.
|
Run verification
Test methods should not call ConfigureAwait(false), as it may bypass parallelization limits. Omit ConfigureAwait, or use ConfigureAwait(true) to avoid CA2007.
|
Run verification
Test methods should not call ConfigureAwait(false), as it may bypass parallelization limits. Omit ConfigureAwait, or use ConfigureAwait(true) to avoid CA2007.
|
Run verification
Test methods should not call ConfigureAwait(false), as it may bypass parallelization limits. Omit ConfigureAwait, or use ConfigureAwait(true) to avoid CA2007.
|
The logs for this run have expired and are no longer available.
Loading