Blackhole post-commit tests #1075
blackhole-post-commit.yaml
on: workflow_dispatch
build-docker-image
/
build-docker-image
18s
static-checks
/
check-spdx-licenses
58s
static-checks
/
check-metal-kernel-count
4s
static-checks
/
check-black
2m 20s
static-checks
/
check-doc
29s
static-checks
/
check-forbidden-imports
8s
static-checks
/
check-sweeps-workflow
8s
umd-unit-tests
/
blackhole BH
1m 38s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
12m 14s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
24 errors and 3 warnings
umd-unit-tests / blackhole BH
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
umd-unit-tests / blackhole BH
The operation was canceled.
|
sd-unit-tests / blackhole BH
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
sd-unit-tests / blackhole BH
The operation was canceled.
|
cpp-unit-tests / C++ blackhole BH
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
cpp-unit-tests / C++ blackhole BH
The operation was canceled.
|
fd-unit-tests / eager trace tests blackhole BH
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
fd-unit-tests / eager trace tests blackhole BH
The operation was canceled.
|
fd-unit-tests / eager unit tests 3 blackhole BH
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
fd-unit-tests / eager unit tests 3 blackhole BH
The operation was canceled.
|
fd-unit-tests / eager unit tests 2 blackhole BH
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
fd-unit-tests / eager unit tests 5 blackhole BH
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
fd-unit-tests / eager unit tests 5 blackhole BH
The operation was canceled.
|
fd-unit-tests / eager unit tests 4 blackhole BH
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
fd-unit-tests / eager unit tests 4 blackhole BH
The operation was canceled.
|
fd-unit-tests / eager unit tests 6 blackhole BH
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
fd-unit-tests / eager unit tests 6 blackhole BH
The operation was canceled.
|
fd-unit-tests / eager unit tests 1 blackhole BH
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
fd-unit-tests / eager unit tests 1 blackhole BH
The operation was canceled.
|
fd-unit-tests / eager unit tests 7 blackhole BH
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
fd-unit-tests / sweep blackhole BH
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
fd-unit-tests / sweep blackhole BH
The operation was canceled.
|
cpp-unit-tests / ttnn ccl cpp unit tests blackhole BH
The self-hosted runner: tt-metal-ci-bm-yyzo-bh-gh04 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
cpp-unit-tests / ttnn cpp tests blackhole BH
The self-hosted runner: tt-metal-ci-bm-yyzo-bh-gh03 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
build-wheels / build-wheel
Cache paths are empty. Please check the previous logs and make sure that the python version is specified
|
build-wheels / build-wheel
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
fd-unit-tests / eager unit tests 6 blackhole BH
No files were found with the provided path: ~/run-log/20241008175324_sys_logs.tar. No artifacts will be uploaded.
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
TTMetal_build_blackhole
Expired
|
46.7 MB |
|
eager-dist-ubuntu-20.04-blackhole
Expired
|
371 MB |
|
test_reports_59fee372-3f65-4303-a7f7-150a3c5e4974
Expired
|
34.9 KB |
|
test_reports_806c8fb8-dd0a-44e5-b57f-2c8da7d6ae4f
Expired
|
5.69 KB |
|
test_reports_978c5119-bdee-42d3-9041-261a63c846f2
Expired
|
4.94 KB |
|
test_reports_9f2ca83d-0244-4143-8c87-aa3fcaad185a
Expired
|
7.11 KB |
|
test_reports_d595b2af-058a-41c1-a9b5-2e58fbee87e8
Expired
|
10.2 KB |
|
test_reports_dd85b1f1-f706-40b1-965a-c6f5631327a1
Expired
|
9.23 KB |
|
test_reports_ec2a484d-973b-4cca-88fc-c4d2be1f9546
Expired
|
875 Bytes |
|
test_reports_ef6282ec-90df-48c4-a3f6-61eda705bc74
Expired
|
3.79 KB |
|
test_reports_ffa40c2b-9321-4750-94d9-49dd6cba69d0
Expired
|
8.2 KB |
|