Process completed with exit code 1.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2, actions/setup-node@v2-beta. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

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> (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2015) [/private/var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/arrow-14.0.2.XXXXX.gkk2MKcf/apache-arrow-14.0.2/csharp/src/Apache.Arrow/Apache.Arrow.csproj::TargetFramework=net6.0]

Nullability of type of parameter 'value' doesn't match overridden member (possibly because of nullability attributes). [/private/var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/arrow-14.0.2.XXXXX.gkk2MKcf/apache-arrow-14.0.2/csharp/test/Apache.Arrow.Flight.Sql.Tests/Apache.Arrow.Flight.Sql.Tests.csproj]

Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)

Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)

Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)

Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)

Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)

Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)

Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)