Skip to content

LambdaLabs Validation Tests #511

LambdaLabs Validation Tests

LambdaLabs Validation Tests #511

Triggered via schedule March 12, 2026 03:06
Status Failure
Total duration 1m 18s
Artifacts
LambdaLabs Provider Validation
1m 13s
LambdaLabs Provider Validation
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 3 warnings
LambdaLabs Provider Validation
Process completed with exit code 1.
LambdaLabs Provider Validation
Cannot open: File exists
LambdaLabs Provider Validation
Cannot open: File exists
LambdaLabs Provider Validation
Cannot open: File exists
LambdaLabs Provider Validation
Cannot open: File exists
LambdaLabs Provider Validation
Cannot open: File exists
LambdaLabs Provider Validation
Cannot open: File exists
LambdaLabs Provider Validation
Cannot open: File exists
LambdaLabs Provider Validation
Cannot open: File exists
LambdaLabs Provider Validation
Cannot open: File exists
LambdaLabs Provider Validation
Cannot open: File exists
LambdaLabs Provider Validation
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-go@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
LambdaLabs Provider Validation
No files were found with the provided path: v1/providers/lambdalabs/coverage.out. No artifacts will be uploaded.
LambdaLabs Provider Validation
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2