Runs on schedule #59
PaddleX_multimodal_pipeline_Run_Check.yml
on: schedule
Matrix: run-check
Annotations
31 errors and 5 notices
|
run-check (ubuntu-24.04-arm, 3.8)
Process completed with exit code 1.
|
|
run-check (ubuntu-latest, 3.8)
Process completed with exit code 1.
|
|
run-check (ubuntu-latest, 3.9)
Process completed with exit code 1.
|
|
run-check (ubuntu-latest, 3.12)
Process completed with exit code 1.
|
|
run-check (ubuntu-latest, 3.11)
Process completed with exit code 1.
|
|
run-check (macos-13, 3.9)
Process completed with exit code 1.
|
|
run-check (ubuntu-24.04-arm, 3.11)
Process completed with exit code 139.
|
|
run-check (ubuntu-24.04-arm, 3.9)
Process completed with exit code 139.
|
|
run-check (macos-13, 3.8)
Process completed with exit code 1.
|
|
run-check (macos-13, 3.10)
Process completed with exit code 1.
|
|
run-check (macos-latest, 3.8)
Process completed with exit code 1.
|
|
run-check (macos-latest, 3.8)
[notice] A new release of pip is available: 21.1.1 -> 25.0.1
[notice] To update, run: python3.8 -m pip install --upgrade pip
|
|
run-check (windows-latest, 3.8)
Process completed with exit code 1.
|
|
run-check (windows-latest, 3.10)
Process completed with exit code 1.
|
|
run-check (ubuntu-24.04-arm, 3.10)
Process completed with exit code 139.
|
|
run-check (ubuntu-24.04-arm, 3.12)
Process completed with exit code 139.
|
|
run-check (ubuntu-latest, 3.10)
Process completed with exit code 1.
|
|
run-check (windows-latest, 3.12)
Process completed with exit code 1.
|
|
run-check (windows-latest, 3.11)
Process completed with exit code 1.
|
|
run-check (macos-latest, 3.12)
Process completed with exit code 1.
|
|
run-check (windows-latest, 3.9)
Process completed with exit code 1.
|
|
run-check (macos-latest, 3.11)
Process completed with exit code 1.
|
|
run-check (macos-latest, 3.9)
Process completed with exit code 1.
|
|
run-check (macos-latest, 3.10)
Process completed with exit code 1.
|
|
run-check (macos-13, 3.12)
Process completed with exit code 1.
|
|
run-check (macos-13, 3.11)
Process completed with exit code 1.
|
|
run-check (ubuntu-20.04, 3.8)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
run-check (ubuntu-20.04, 3.10)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
run-check (ubuntu-20.04, 3.9)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
run-check (ubuntu-20.04, 3.12)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
run-check (ubuntu-20.04, 3.11)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
run-check (windows-latest, 3.8)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
run-check (windows-latest, 3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
run-check (windows-latest, 3.12)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
run-check (windows-latest, 3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
run-check (windows-latest, 3.9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|