Skip to content

Keep failed transaction lines eligible for retry #307

Keep failed transaction lines eligible for retry

Keep failed transaction lines eligible for retry #307

Triggered via pull request September 16, 2026 13:41
Status Success
Total duration 12m 35s
Artifacts 1

pullrequest.yml

on: pull_request
Build and Test Pull Requests
12m 31s
Build and Test Pull Requests
Fit to window
Zoom out
Zoom in

Annotations

21 warnings
Build and Test Pull Requests
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-dotnet@v4, actions/upload-artifact@v4, actions/upload-artifact@v4.4.0, dorny/test-reporter@v1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/FileProcessorSteps.cs#L153
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/FileProcessorSteps.cs#L124
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/FileProcessorSteps.cs#L97
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/SpecflowExtensions.cs#L132
Non-nullable property 'LineData' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/SpecflowExtensions.cs#L93
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/SpecflowExtensions.cs#L63
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.BusinessLogic/Managers/FileProcessorManager.cs#L81
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests: FileProcessor.FileProfileAggregate/FileProfileAggregate.cs#L305
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests: FileProcessor.FileProfileAggregate/FileProfileAggregate.cs#L161
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

Artifacts

Produced during runtime
Name Size Digest
tracelogs
285 KB
sha256:d6c9d75fdac88db61e111715d57f8fa8c777fc62c9b1362dbe83f07072263c6d