Skip to content

refactor: make transfer module v2 use same core paths as v1 #26244

refactor: make transfer module v2 use same core paths as v1

refactor: make transfer module v2 use same core paths as v1 #26244

Triggered via pull request January 11, 2025 22:05
Status Success
Total duration 13m 27s
Artifacts 8

test.yml

on: pull_request
split-test-files
28s
split-test-files
cleanup-runs
5s
cleanup-runs
Matrix: build
Matrix: tests
code-analysis
1m 4s
code-analysis
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
cleanup-runs
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
split-test-files
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
tests (03)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
tests (01)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build (arm64)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build (amd64)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
tests (02)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
tests (00)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
code-analysis
Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/[email protected]. Please update your workflow to use either v3 or v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down
SonarScanner
This action is deprecated and will be removed in a future release. Please use the sonarqube-scan-action action instead. The sonarqube-scan-action is a drop-in replacement for this action.

Artifacts

Produced during runtime
Name Size
0f579fb6de9655ff1898c8af542d066c369e8a42-00
324 Bytes
0f579fb6de9655ff1898c8af542d066c369e8a42-00-coverage
47 KB
0f579fb6de9655ff1898c8af542d066c369e8a42-01
324 Bytes
0f579fb6de9655ff1898c8af542d066c369e8a42-01-coverage
146 KB
0f579fb6de9655ff1898c8af542d066c369e8a42-02
314 Bytes
0f579fb6de9655ff1898c8af542d066c369e8a42-02-coverage
189 KB
0f579fb6de9655ff1898c8af542d066c369e8a42-03
361 Bytes
0f579fb6de9655ff1898c8af542d066c369e8a42-03-coverage
46.6 KB