Skip to content

Fix upload temporary file handling #327

Fix upload temporary file handling

Fix upload temporary file handling #327

Triggered via pull request October 15, 2026 12:40
Status Success
Total duration 12m 59s
Artifacts 2

pullrequest.yml

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

Annotations

21 warnings and 1 notice
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#L195
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/FileProcessorSteps.cs#L185
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/FileProcessorSteps.cs#L156
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/FileProcessorSteps.cs#L129
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.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"

Artifacts

Produced during runtime
Name Size Digest
test-results
19 KB
sha256:841871d46a8bf3384d6024f58f5ca895bb371abcaa559672060cd688aaa3c265
tracelogs
263 KB
sha256:47783968cca92de28373b90f501f5a66bd7bc859d23432a4937cd3b4f4df624e