ttnn - Run sweeps #2392
Triggered via schedule
February 13, 2025 21:04
jdesousa-TT
Status
Failure
Total duration
12h 21m 48s
Artifacts
1
ttnn-run-sweeps.yaml
on: schedule
build-artifact
/
...
/
check-docker-images
9s
build-artifact
/
🛠️ Build Release ubuntu 20.04
9m 41s
Matrix: ttnn-run-sweeps
Annotations
12 errors, 1 warning, and 15 notices
|
ttnn-run-sweeps (Wormhole N300 Sweeps, wormhole_b0, cloud-virtual-machine, N300, in-service, tt-s...
The job running on runner tt-metal-ci-vm-150 has exceeded the maximum execution time of 720 minutes.
|
|
pcie-cards-are-being-used-cleanup
This can happen if a test hung and is normally an issue with the test, rather than infra. Tenstorrent cards seem to be in use. Killing PIDs and exiting unsuccessfully.
|
|
ttnn-run-sweeps (Wormhole N300 Sweeps, wormhole_b0, cloud-virtual-machine, N300, in-service, tt-s...
Process completed with exit code 1.
|
|
ttnn-run-sweeps (Wormhole N300 Sweeps, wormhole_b0, cloud-virtual-machine, N300, in-service, tt-s...
The operation was canceled.
|
|
ttnn-run-sweeps (Grayskull E150 Sweeps, grayskull, cloud-virtual-machine, E150, in-service, tt-sm...
The job running on runner tt-metal-ci-vm-4 has exceeded the maximum execution time of 720 minutes.
|
|
pcie-cards-are-being-used-cleanup
This can happen if a test hung and is normally an issue with the test, rather than infra. Tenstorrent cards seem to be in use. Killing PIDs and exiting unsuccessfully.
|
|
ttnn-run-sweeps (Grayskull E150 Sweeps, grayskull, cloud-virtual-machine, E150, in-service, tt-sm...
Process completed with exit code 1.
|
|
ttnn-run-sweeps (Grayskull E150 Sweeps, grayskull, cloud-virtual-machine, E150, in-service, tt-sm...
The operation was canceled.
|
|
ttnn-run-sweeps (Wormhole N150 Sweeps, wormhole_b0, cloud-virtual-machine, N150, in-service, tt-s...
The job running on runner tt-metal-ci-vm-13 has exceeded the maximum execution time of 720 minutes.
|
|
pcie-cards-are-being-used-cleanup
This can happen if a test hung and is normally an issue with the test, rather than infra. Tenstorrent cards seem to be in use. Killing PIDs and exiting unsuccessfully.
|
|
ttnn-run-sweeps (Wormhole N150 Sweeps, wormhole_b0, cloud-virtual-machine, N150, in-service, tt-s...
Process completed with exit code 1.
|
|
ttnn-run-sweeps (Wormhole N150 Sweeps, wormhole_b0, cloud-virtual-machine, N150, in-service, tt-s...
The operation was canceled.
|
|
hugepages-service-not-found-startup
Hugepages service not found. Using old rc.local method
|
|
printing-out-smi-info-cleanup
Touching and printing out SMI info
|
|
disk-usage-after-startup
Disk usage is 84 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
reset-successful-startup
tt-smi reset was successful
|
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
|
hugepages-setup-success-startup
Hugepages is now setup.
|
|
disk-usage-after-startup
Disk usage is 59 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
reset-successful-startup
tt-smi reset was successful
|
|
hugepages-setup-success-startup
Hugepages is now setup.
|
|
disk-usage-after-startup
Disk usage is 76 %
|
|
printing-smi-info-startup
Touching and printing out SMI info
|
|
reset-successful-startup
tt-smi reset was successful
|
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
|
hugepages-setup-success-startup
Hugepages is now setup.
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
TTMetal_build_any
|
164 MB |
|