Process completed with exit code 1.

The job running on runner GitHub Actions 12 has exceeded the maximum execution time of 15 minutes.

The operation was canceled.

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

Type parameter 'T' has the same name as the type parameter from outer type 'SocketWireTestBase<T>'

Type parameter 'T' has the same name as the type parameter from outer type 'SocketWireTestBase<T>'

'WireBase.WireBase(IScheduler)' is obsolete

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'

The variable 'entity_id' is assigned but its value is never used

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

This call site is reachable on all platforms. 'Console.Title.get' is only supported on: 'windows'. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1416)

Type parameter 'T' has the same name as the type parameter from outer type 'SocketWireTestBase<T>'

Type parameter 'T' has the same name as the type parameter from outer type 'SocketWireTestBase<T>'

'WireBase.WireBase(IScheduler)' is obsolete

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

No files were found with the provided path: **/TestResults/*. No artifacts will be uploaded.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

Type parameter 'T' has the same name as the type parameter from outer type 'SocketWireTestBase<T>'

Type parameter 'T' has the same name as the type parameter from outer type 'SocketWireTestBase<T>'

'WireBase.WireBase(IScheduler)' is obsolete

'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'

The variable 'entity_id' is assigned but its value is never used

'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

This call site is reachable on all platforms. 'Console.Title.get' is only supported on: 'windows'. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1416)

Type parameter 'T' has the same name as the type parameter from outer type 'SocketWireTestBase<T>'

Type parameter 'T' has the same name as the type parameter from outer type 'SocketWireTestBase<T>'

'WireBase.WireBase(IScheduler)' is obsolete

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.