Stake Table Integration test #25
Triggered via pull request
February 17, 2025 11:24
Status
Failure
Total duration
41m 31s
Artifacts
–
hotshot.yml
on: pull_request
test-examples
9m 14s
Matrix: test
Annotations
14 errors
test (test-ci-6-3)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
test (test-ci-6-3)
Process completed with exit code 143.
|
test (test-ci-6-5)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
test (test-ci-6-5)
Process completed with exit code 143.
|
test (test-ci-6-1)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
test (test-ci-6-1)
Process completed with exit code 143.
|
test (test-ci-6-4)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
test (test-ci-6-4)
Process completed with exit code 143.
|
test (test-ci-6-6)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
test (test-ci-6-6)
Process completed with exit code 143.
|
test (test-ci-6-2)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
test (test-ci-6-2)
Process completed with exit code 143.
|
test (test-ci-rest)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
test (test-ci-rest)
Process completed with exit code 143.
|