Repository navigation
ability to replay unprocessed file lines #315
Triggered via pull request
September 25, 2026 18:54
StuartFerguson
Status
Failure
Total duration
25m 4s
Artifacts
–
pullrequest.yml
on: pull_request
Build and Test Pull Requests
25m 1s
Annotations
1 error, 21 warnings, and 1 notice
|
Build and Test Pull Requests
Process completed with exit code 2.
|
|
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, 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#L163
Converting null literal or possible null value to non-nullable type.
|
|
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#L94
Dereference of a possibly null reference.
|
|
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.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.
|
|
Build and Test Pull Requests
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
|