Skip to content

Use ldata node name when downloading LatchFile to local in the case of absolute node path #2091

Use ldata node name when downloading LatchFile to local in the case of absolute node path

Use ldata node name when downloading LatchFile to local in the case of absolute node path #2091

Triggered via pull request July 11, 2023 05:16
@AidanAbdAidanAbd
synchronize #295
Status Failure
Total duration 1d 6h 28m 48s
Artifacts

test.yaml

on: pull_request_target
Matrix: Test Linux
Matrix: Test MacOs
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
Test MacOs (3.8, macos-10.15)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
Test Linux (3.8, ubuntu-18.04)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
Test MacOs (3.9, macos-10.15)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
Test Linux (3.9, ubuntu-18.04)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
Test
The ubuntu-18.04 environment is deprecated, consider switching to ubuntu-20.04(ubuntu-latest), or ubuntu-22.04 instead. For more details see https://github.com/actions/virtual-environments/issues/6002
Test
The macOS-10.15 environment is deprecated, consider switching to macos-11(macos-latest), macos-12 instead. For more details see https://github.com/actions/virtual-environments/issues/5583