Blackhole post-commit tests #1030
blackhole-post-commit.yaml
on: schedule
build-docker-image
/
build-docker-image
46s
static-checks
/
check-spdx-licenses
50s
static-checks
/
check-metal-kernel-count
6s
static-checks
/
check-black
37s
static-checks
/
check-doc
12s
static-checks
/
check-forbidden-imports
8s
static-checks
/
check-sweeps-workflow
6s
umd-unit-tests
/
blackhole BH
1m 38s
Matrix: build-artifact / build-artifact
sd-unit-tests
/
blackhole BH
11m 22s
Matrix: cpp-unit-tests / models
Matrix: fd-unit-tests / fd-tests
Annotations
26 errors and 4 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.
|
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.
|
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.
|
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 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 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 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 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 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 / eager unit tests 7 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 / 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 cpp 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.
|
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/20241005083240_sys_logs.tar. No artifacts will be uploaded.
|
fd-unit-tests / eager unit tests 7 blackhole BH
No files were found with the provided path: ~/run-log/20241005083455_sys_logs.tar. No artifacts will be uploaded.
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
TTMetal_build_blackhole
Expired
|
48.6 MB |
|
eager-dist-ubuntu-20.04-blackhole
Expired
|
371 MB |
|
test_reports_0d72f83d-7b28-4265-83f9-ac10a7beb52a
Expired
|
3.85 KB |
|
test_reports_2caf3d38-3014-4308-b7f8-ad0c572ceced
Expired
|
34.7 KB |
|
test_reports_4f9dbfc5-26c9-4880-aa63-00c8f050b5ed
Expired
|
1.17 KB |
|
test_reports_590cb98f-a7a2-426a-a6b9-87002420d1c4
Expired
|
7.19 KB |
|
test_reports_59637302-1e76-4cc6-b255-fcde72e5a056
Expired
|
8.23 KB |
|
test_reports_5d14423c-5d78-46df-b5ae-712c2831ad31
Expired
|
10.1 KB |
|
test_reports_9096c391-0508-49d6-8428-c126bba36614
Expired
|
4.94 KB |
|
test_reports_ad92654a-473a-48c9-a859-c68f0ea3b18f
Expired
|
9.28 KB |
|
test_reports_ba864f77-16af-441d-bdbf-b2c9f5316016
Expired
|
877 Bytes |
|