All post-commit tests #22115
all-post-commit-workflows.yaml
on: workflow_dispatch
build-docker-image-2004
/
build-docker-image
21s
build-docker-image-2204
/
build-docker-image
24s
static-checks
/
Run Pre-commit Hooks
22s
static-checks
/
check-black
2s
static-checks
/
check-spdx-licenses
52s
static-checks
/
check-metal-kernel-count
8s
static-checks
/
check-doc
15s
static-checks
/
check-forbidden-imports
9s
static-checks
/
check-sweeps-workflow
9s
static-checks
/
cmake-version
50s
static-checks
/
clang-tidy
0s
build-artifact-profiler
/
...
/
build-docker-image
code-analysis
/
...
/
build-docker-image
20s
Matrix: build-artifact-profiler / build-artifact
Matrix: build-artifact / build-artifact
code-analysis
/
clang-tidy
58m 19s
Matrix: profiler-regression / profiler-regression
Matrix: build-wheels
Matrix: build-docs / build-deploy-docs
Matrix: cpp-unit-tests
Matrix: sd-unit-tests
Matrix: tt-train-cpp-unit-tests
Matrix: build / build-lib
Matrix: fast-dispatch-unit-tests
Waiting for pending jobs
Matrix: models-unit-tests
Waiting for pending jobs
Matrix: test-wheels / test-wheels-host
Waiting for pending jobs
Matrix: test-wheels / test-wheels-silicon
Waiting for pending jobs
Matrix: ttnn-unit-tests
Waiting for pending jobs
Annotations
27 errors, 13 warnings, and 91 notices
build-wheels (ubuntu-20.04, wormhole_b0) / build-wheel
System.IO.IOException: No space left on device : '/home/runner/runners/2.321.0/_diag/Worker_20241211-163212-utc.log'
at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset)
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.Diagnostics.TextWriterTraceListener.Flush()
at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id)
at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message)
at GitHub.Runner.Worker.Worker.RunAsync(String pipeIn, String pipeOut)
at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args)
System.IO.IOException: No space left on device : '/home/runner/runners/2.321.0/_diag/Worker_20241211-163212-utc.log'
at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset)
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.Diagnostics.TextWriterTraceListener.Flush()
at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id)
at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message)
at GitHub.Runner.Common.Tracing.Error(Exception exception)
at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args)
Unhandled exception. System.IO.IOException: No space left on device : '/home/runner/runners/2.321.0/_diag/Worker_20241211-163212-utc.log'
at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset)
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.Diagnostics.TextWriterTraceListener.Flush()
at System.Diagnostics.TraceSource.Flush()
at GitHub.Runner.Common.Tracing.Dispose(Boolean disposing)
at GitHub.Runner.Common.Tracing.Dispose()
at GitHub.Runner.Common.TraceManager.Dispose(Boolean disposing)
at GitHub.Runner.Common.TraceManager.Dispose()
at GitHub.Runner.Common.HostContext.Dispose(Boolean disposing)
at GitHub.Runner.Common.HostContext.Dispose()
at GitHub.Runner.Worker.Program.Main(String[] args)
|
build-wheels (ubuntu-20.04, grayskull) / build-wheel
FailFast: cancelling since parallel instance has failed
|
sd-unit-tests (wormhole_b0, N150) / wormhole_b0 N150
Process completed with exit code 1.
|
cpp-unit-tests (grayskull, E150) / C++ grayskull E150
The run was canceled by @eyonland.
|
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.
|
cpp-unit-tests (grayskull, E150) / C++ grayskull E150
Process completed with exit code 1.
|
cpp-unit-tests (grayskull, E150) / C++ grayskull E150
The operation was canceled.
|
cpp-unit-tests (grayskull, E150) / ttnn ccl cpp unit tests grayskull E150
The run was canceled by @eyonland.
|
cpp-unit-tests (grayskull, E150) / ttnn ccl cpp unit tests grayskull E150
The operation was canceled.
|
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.
|
cpp-unit-tests (grayskull, E150) / ttnn ccl cpp unit tests grayskull E150
Process completed with exit code 1.
|
cpp-unit-tests (wormhole_b0, N300) / C++ wormhole_b0 N300
The run was canceled by @eyonland.
|
cpp-unit-tests (wormhole_b0, N300) / C++ wormhole_b0 N300
The operation was canceled.
|
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.
|
cpp-unit-tests (wormhole_b0, N300) / C++ wormhole_b0 N300
Process completed with exit code 1.
|
sd-unit-tests (grayskull, E150) / grayskull E150
The run was canceled by @eyonland.
|
cpp-unit-tests (wormhole_b0, N150) / C++ wormhole_b0 N150
The run was canceled by @eyonland.
|
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.
|
sd-unit-tests (grayskull, E150) / grayskull E150
Process completed with exit code 1.
|
cpp-unit-tests (wormhole_b0, N150) / C++ wormhole_b0 N150
The operation was canceled.
|
sd-unit-tests (grayskull, E150) / grayskull E150
The operation was canceled.
|
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.
|
cpp-unit-tests (wormhole_b0, N150) / C++ wormhole_b0 N150
Process completed with exit code 1.
|
sd-unit-tests (wormhole_b0, N300) / wormhole_b0 N300
The run was canceled by @eyonland.
|
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.
|
sd-unit-tests (wormhole_b0, N300) / wormhole_b0 N300
Process completed with exit code 1.
|
sd-unit-tests (wormhole_b0, N300) / wormhole_b0 N300
The operation was canceled.
|
static-checks / check-black
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
static-checks / check-forbidden-imports
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
static-checks / check-doc
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
static-checks / check-metal-kernel-count
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
static-checks / check-spdx-licenses
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
static-checks / Run Pre-commit Hooks
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
static-checks / Run Pre-commit Hooks
Unexpected input(s) 'fetch-refs', valid inputs are ['repository', 'ref', 'token', 'ssh-key', 'ssh-known-hosts', 'ssh-strict', 'ssh-user', 'persist-credentials', 'path', 'clean', 'filter', 'sparse-checkout', 'sparse-checkout-cone-mode', 'fetch-depth', 'fetch-tags', 'show-progress', 'lfs', 'submodules', 'set-safe-directory', 'github-server-url']
|
static-checks / Run Pre-commit Hooks
Unexpected input(s) 'fetch-refs', valid inputs are ['repository', 'ref', 'token', 'ssh-key', 'ssh-known-hosts', 'ssh-strict', 'ssh-user', 'persist-credentials', 'path', 'clean', 'filter', 'sparse-checkout', 'sparse-checkout-cone-mode', 'fetch-depth', 'fetch-tags', 'show-progress', 'lfs', 'submodules', 'set-safe-directory', 'github-server-url']
|
static-checks / check-sweeps-workflow
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
build-wheels (ubuntu-20.04, wormhole_b0) / build-wheel
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
build-wheels (ubuntu-20.04, grayskull) / build-wheel
Runner GitHub Actions 14 did not respond to a cancelation request with 00:05:00.
|
build-wheels (ubuntu-20.04, grayskull) / build-wheel
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
sd-unit-tests (wormhole_b0, N150) / wormhole_b0 N150
No files were found with the provided path: ~/run-log/20241211170458_sys_logs.tar. No artifacts will be uploaded.
|
disk-usage-before-startup
Disk usage is 79 %
|
disk-usage-after-startup
Disk usage is 79 %
|
printing-smi-info-startup
Touching and printing out SMI info
|
reset-successful-startup
tt-smi reset was successful
|
printing-out-smi-info-cleanup
Touching and printing out SMI info
|
successful-reset-cleanup
tt-smi reset was successful
|
reset-successful-cleanup
tt-smi reset was successful
|
disk-usage-before-startup
Disk usage is 73 %
|
disk-usage-after-startup
Disk usage is 73 %
|
printing-smi-info-startup
Touching and printing out SMI info
|
reset-successful-startup
tt-smi reset was successful
|
printing-out-smi-info-cleanup
Touching and printing out SMI info
|
successful-reset-cleanup
tt-smi reset was successful
|
reset-successful-cleanup
tt-smi reset was successful
|
disk-usage-before-startup
Disk usage is 70 %
|
disk-usage-after-startup
Disk usage is 70 %
|
printing-smi-info-startup
Touching and printing out SMI info
|
reset-successful-startup
tt-smi reset was successful
|
printing-out-smi-info-cleanup
Touching and printing out SMI info
|
successful-reset-cleanup
tt-smi reset was successful
|
reset-successful-cleanup
tt-smi reset was successful
|
printing-out-smi-info-cleanup
Touching and printing out SMI info
|
successful-reset-cleanup
tt-smi reset was successful
|
reset-successful-cleanup
tt-smi reset was successful
|
disk-usage-before-startup
Disk usage is 67 %
|
disk-usage-after-startup
Disk usage is 67 %
|
printing-smi-info-startup
Touching and printing out SMI info
|
reset-successful-startup
tt-smi reset was successful
|
disk-usage-before-startup
Disk usage is 64 %
|
disk-usage-after-startup
Disk usage is 64 %
|
printing-smi-info-startup
Touching and printing out SMI info
|
reset-successful-startup
tt-smi reset was successful
|
printing-out-smi-info-cleanup
Touching and printing out SMI info
|
successful-reset-cleanup
tt-smi reset was successful
|
reset-successful-cleanup
tt-smi reset was successful
|
printing-out-smi-info-cleanup
Touching and printing out SMI info
|
successful-reset-cleanup
tt-smi reset was successful
|
reset-successful-cleanup
tt-smi reset was successful
|
disk-usage-before-startup
Disk usage is 76 %
|
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
|
disk-usage-before-startup
Disk usage is 87 %
|
disk-usage-after-startup
Disk usage is 87 %
|
disk-usage-before-startup
Disk usage is 80 %
|
printing-smi-info-startup
Touching and printing out SMI info
|
disk-usage-after-startup
Disk usage is 80 %
|
reset-successful-startup
tt-smi reset was successful
|
printing-smi-info-startup
Touching and printing out SMI info
|
printing-out-smi-info-cleanup
Touching and printing out SMI info
|
reset-successful-startup
tt-smi reset was successful
|
successful-reset-cleanup
tt-smi reset was successful
|
printing-out-smi-info-cleanup
Touching and printing out SMI info
|
reset-successful-cleanup
tt-smi reset was successful
|
successful-reset-cleanup
tt-smi reset was successful
|
reset-successful-cleanup
tt-smi reset was successful
|
disk-usage-before-startup
Disk usage is 78 %
|
disk-usage-after-startup
Disk usage is 78 %
|
printing-smi-info-startup
Touching and printing out SMI info
|
reset-successful-startup
tt-smi reset was successful
|
printing-out-smi-info-cleanup
Touching and printing out SMI info
|
successful-reset-cleanup
tt-smi reset was successful
|
reset-successful-cleanup
tt-smi reset was successful
|
disk-usage-before-startup
Disk usage is 79 %
|
disk-usage-after-startup
Disk usage is 79 %
|
printing-smi-info-startup
Touching and printing out SMI info
|
reset-successful-startup
tt-smi reset was successful
|
disk-usage-before-startup
Disk usage is 62 %
|
disk-usage-after-startup
Disk usage is 62 %
|
printing-smi-info-startup
Touching and printing out SMI info
|
reset-successful-startup
tt-smi reset was successful
|
disk-usage-before-startup
Disk usage is 67 %
|
disk-usage-after-startup
Disk usage is 67 %
|
printing-smi-info-startup
Touching and printing out SMI info
|
reset-successful-startup
tt-smi reset was successful
|
disk-usage-before-startup
Disk usage is 72 %
|
disk-usage-after-startup
Disk usage is 72 %
|
printing-smi-info-startup
Touching and printing out SMI info
|
reset-successful-startup
tt-smi reset was successful
|
disk-usage-before-startup
Disk usage is 72 %
|
disk-usage-after-startup
Disk usage is 72 %
|
printing-smi-info-startup
Touching and printing out SMI info
|
disk-usage-before-startup
Disk usage is 74 %
|
reset-successful-startup
tt-smi reset was successful
|
disk-usage-after-startup
Disk usage is 74 %
|
printing-smi-info-startup
Touching and printing out SMI info
|
reset-successful-startup
tt-smi reset was successful
|
disk-usage-before-startup
Disk usage is 77 %
|
disk-usage-after-startup
Disk usage is 77 %
|
printing-smi-info-startup
Touching and printing out SMI info
|
reset-successful-startup
tt-smi reset was successful
|