Skip to content

Fixed failing tests on pytorch nightly using torch.load #5272

Fixed failing tests on pytorch nightly using torch.load

Fixed failing tests on pytorch nightly using torch.load #5272

Triggered via pull request November 7, 2024 11:27
Status Cancelled
Total duration 5m 24s
Artifacts

unit-tests.yml

on: pull_request
Matrix: cpu-tests
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 9 warnings
cpu-tests (macos-latest, pytorch, 3.11, 1)
Process completed with exit code 1.
cpu-tests (ubuntu-latest, 3.11, pytorch-nightly)
Process completed with exit code 1.
cpu-tests (ubuntu-latest, 3.10, pytorch)
Process completed with exit code 1.
cpu-tests (ubuntu-latest, 3.11, pytorch)
Process completed with exit code 1.
cpu-tests (ubuntu-latest, 3.10, pytorch-nightly)
Process completed with exit code 1.
cpu-tests (ubuntu-latest, 3.12, pytorch)
Process completed with exit code 1.
cpu-tests (ubuntu-latest, 3.12, pytorch-nightly)
Process completed with exit code 1.
cpu-tests (ubuntu-latest, 3.9, pytorch)
Process completed with exit code 1.
cpu-tests (ubuntu-latest, 3.9, pytorch-nightly)
Process completed with exit code 1.
cpu-tests (windows-latest, pytorch, 3.11, 1)
Canceling since a higher priority waiting request for 'unit-tests-3299/merge-true' exists
cpu-tests (windows-latest, pytorch, 3.11, 1)
The operation was canceled.
cpu-tests (macos-latest, pytorch, 3.11, 1)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, 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/
cpu-tests (ubuntu-latest, 3.11, pytorch-nightly)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, 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/
cpu-tests (ubuntu-latest, 3.10, pytorch)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, 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/
cpu-tests (ubuntu-latest, 3.11, pytorch)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, 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/
cpu-tests (ubuntu-latest, 3.10, pytorch-nightly)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, 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/
cpu-tests (ubuntu-latest, 3.12, pytorch)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, 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/
cpu-tests (ubuntu-latest, 3.12, pytorch-nightly)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, 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/
cpu-tests (ubuntu-latest, 3.9, pytorch)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, 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/
cpu-tests (ubuntu-latest, 3.9, pytorch-nightly)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, 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/