Skip to content
Build Centos7 Releases

add --allow-no-vcs to cargo fix command (#570) #203

Sign in to view logs

add --allow-no-vcs to cargo fix command (#570)

add --allow-no-vcs to cargo fix command (#570) #203

Triggered via push September 14, 2024 07:02
@lihao712lihao712
pushed dce12db
master
Status Failure
Total duration 1m 10s
Artifacts –

build-ce7-releases.yml

on: push
Matrix: Build Snapshot
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 2 warnings
Build Snapshot (spark303, 3.0.1)
Process completed with exit code 127.
Build Snapshot (spark333, 3.0.1)
Process completed with exit code 127.
Build Snapshot (spark351, 3.0.1)
The job was canceled because "spark303_3_0_1" failed.
Build Snapshot (spark351, 3.0.1)
Process completed with exit code 127.
Build Snapshot (spark320, 3.0.1)
The job was canceled because "spark303_3_0_1" failed.
Build Snapshot (spark320, 3.0.1)
Process completed with exit code 127.
Build Snapshot (spark324, 3.0.1)
The job was canceled because "spark303_3_0_1" failed.
Build Snapshot (spark303, 3.0.1)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build Snapshot (spark333, 3.0.1)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/