Process completed with exit code 1.

'FakeImageOperationsProvider.FakeImageOperations<Rgba32>' does not contain a definition for 'SetShapeOptions' and no accessible extension method 'SetShapeOptions' accepting a first argument of type 'FakeImageOperationsProvider.FakeImageOperations<Rgba32>' could be found (are you missing a using directive or an assembly reference?)

'FakeImageOperationsProvider.FakeImageOperations<Rgba32>' does not contain a definition for 'SetShapeOptions' and no accessible extension method 'SetShapeOptions' accepting a first argument of type 'FakeImageOperationsProvider.FakeImageOperations<Rgba32>' could be found (are you missing a using directive or an assembly reference?)

The strategy configuration was canceled because "Build.ubuntu-latest_net10_0_10_" failed

The operation was canceled.

The strategy configuration was canceled because "Build.ubuntu-latest_net10_0_10_" failed

The operation was canceled.

The strategy configuration was canceled because "Build.ubuntu-latest_net10_0_10_" failed

The operation was canceled.

The strategy configuration was canceled because "Build.ubuntu-latest_net10_0_10_" failed

The operation was canceled.

The strategy configuration was canceled because "Build.ubuntu-latest_net10_0_10_" failed

The operation was canceled.

'FakeImageOperationsProvider.FakeImageOperations<Rgba32>' does not contain a definition for 'SetShapeOptions' and no accessible extension method 'SetShapeOptions' accepting a first argument of type 'FakeImageOperationsProvider.FakeImageOperations<Rgba32>' could be found (are you missing a using directive or an assembly reference?)

'FakeImageOperationsProvider.FakeImageOperations<Rgba32>' does not contain a definition for 'SetShapeOptions' and no accessible extension method 'SetShapeOptions' accepting a first argument of type 'FakeImageOperationsProvider.FakeImageOperations<Rgba32>' could be found (are you missing a using directive or an assembly reference?)

The strategy configuration was canceled because "Build.ubuntu-latest_net10_0_10_" failed

The operation was canceled.

'FakeImageOperationsProvider.FakeImageOperations<Rgba32>' does not contain a definition for 'SetShapeOptions' and no accessible extension method 'SetShapeOptions' accepting a first argument of type 'FakeImageOperationsProvider.FakeImageOperations<Rgba32>' could be found (are you missing a using directive or an assembly reference?)

'FakeImageOperationsProvider.FakeImageOperations<Rgba32>' does not contain a definition for 'SetShapeOptions' and no accessible extension method 'SetShapeOptions' accepting a first argument of type 'FakeImageOperationsProvider.FakeImageOperations<Rgba32>' could be found (are you missing a using directive or an assembly reference?)

The strategy configuration was canceled because "Build.ubuntu-latest_net10_0_10_" failed

The operation was canceled.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4, NuGet/setup-nuget@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

No files were found with the provided path: tests/Images/ActualOutput/. No artifacts will be uploaded.

Converting null literal or possible null value to non-nullable type.

Converting null literal or possible null value to non-nullable type.

Argument of type '(GraphicsPath sdPath, SolidBrush? fill, Pen? stroke)' cannot be used for parameter 'item' of type '(GraphicsPath, SolidBrush, Pen)' in 'void List<(GraphicsPath, SolidBrush, Pen)>.Add((GraphicsPath, SolidBrush, Pen) item)' due to differences in the nullability of reference types.

Converting null literal or possible null value to non-nullable type.

Converting null literal or possible null value to non-nullable type.

Argument of type '(SKPath skPath, SKPaint? fillPaint, SKPaint? strokePaint)' cannot be used for parameter 'item' of type '(SKPath, SKPaint, SKPaint)' in 'void List<(SKPath, SKPaint, SKPaint)>.Add((SKPath, SKPaint, SKPaint) item)' due to differences in the nullability of reference types.

Converting null literal or possible null value to non-nullable type.

Converting null literal or possible null value to non-nullable type.

Non-nullable field 'bytes' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Converting null literal or possible null value to non-nullable type.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-dotnet@v4, NuGet/setup-nuget@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-dotnet@v4, NuGet/setup-nuget@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-dotnet@v4, NuGet/setup-nuget@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-dotnet@v4, NuGet/setup-nuget@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-dotnet@v4, NuGet/setup-nuget@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

The parameters should all be placed on the same line or each parameter should be placed on its own line (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1117.md)

The parameters should all be placed on the same line or each parameter should be placed on its own line (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1117.md)

The parameters should all be placed on the same line or each parameter should be placed on its own line (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1117.md)

The parameters should all be placed on the same line or each parameter should be placed on its own line (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1117.md)

The behavior of 'string.StartsWith(string)' could vary based on the current user's locale settings. Replace this call in 'SixLabors.ImageSharp.Drawing.Tests.TestEnvironment.IsFramework.get' with a call to 'string.StartsWith(string, System.StringComparison)'. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1310)

Single-line comments should not be followed by blank line (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1512.md)

Code should not contain multiple blank lines in a row (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1507.md)

File name should match first type name (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1649.md)

Single line comment should begin with a space (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1005.md)

Single-line comments should not be followed by blank line (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1512.md)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-dotnet@v4, NuGet/setup-nuget@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

The parameters should all be placed on the same line or each parameter should be placed on its own line (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1117.md)

The parameters should all be placed on the same line or each parameter should be placed on its own line (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1117.md)

The parameters should all be placed on the same line or each parameter should be placed on its own line (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1117.md)

The parameters should all be placed on the same line or each parameter should be placed on its own line (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1117.md)

The parameters should all be placed on the same line or each parameter should be placed on its own line (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1117.md)

Single-line comments should not be followed by blank line (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1512.md)

Code should not contain multiple blank lines in a row (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1507.md)

File name should match first type name (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1649.md)

Single line comment should begin with a space (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1005.md)

Single-line comments should not be followed by blank line (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1512.md)