Blackhole post-commit tests #1063
blackhole-post-commit.yaml
on: workflow_dispatch
build-docker-image
/
build-docker-image
15s
static-checks
/
check-spdx-licenses
47s
static-checks
/
check-metal-kernel-count
7s
static-checks
/
check-black
37s
static-checks
/
check-doc
14s
static-checks
/
check-forbidden-imports
7s
static-checks
/
check-sweeps-workflow
6s
umd-unit-tests
/
blackhole BH
1m 48s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
11m 17s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
22 errors and 7 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.
|
cpp-unit-tests / ttnn ccl cpp 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.
|
cpp-unit-tests / ttnn cpp 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.
|
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 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 2 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 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 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 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 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 / 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.
|
fd-unit-tests / eager unit tests 1 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.
|
fd-unit-tests / eager unit tests 7 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.
|
build-docker-image / build-docker-image
Unable to find merge base between d7a12ee9eba4e17158d7e6731ce09d48be90eac4 and 9a68fd09d8ee2d81c445c576861cf146c9b54810
|
build-docker-image / build-docker-image
Set 'fetch_additional_submodule_history: true' to fetch additional submodule history for: tt_metal/third_party/tt_llk_blackhole
|
build-docker-image / build-docker-image
Unable to find merge base between 3457491ab21aecd4325851c2607c35582f89e111 and 166515054c09553317f569d3689198c3891cefe0
|
build-docker-image / build-docker-image
Set 'fetch_additional_submodule_history: true' to fetch additional submodule history for: tt_metal/third_party/tt_llk_wormhole_b0
|
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/20241007213826_sys_logs.tar. No artifacts will be uploaded.
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
TTMetal_build_blackhole
Expired
|
46.9 MB |
|
eager-dist-ubuntu-20.04-blackhole
Expired
|
371 MB |
|
test_reports_1f501861-0ecb-47e3-a77b-fb8bc2ae0a90
Expired
|
9.22 KB |
|
test_reports_627d7e7c-ff8f-4511-9403-5737f87bba99
Expired
|
8.22 KB |
|
test_reports_62a074b4-051b-4672-80f7-bef46d30152f
Expired
|
10.2 KB |
|
test_reports_81b33f15-9f66-4fb3-b4e9-acd96a0c5b14
Expired
|
3.79 KB |
|
test_reports_ad8098a0-1ca2-40ae-9801-d5718c31e9b1
Expired
|
876 Bytes |
|
test_reports_dbec85b5-47ed-4d99-bea9-f1a7af2e249e
Expired
|
36.2 KB |
|
test_reports_e1df5c96-7436-4013-8483-ee88f2525590
Expired
|
4.94 KB |
|