Skip to content

Workflow updates and standardized pre-commit changes and configurations added #3

Workflow updates and standardized pre-commit changes and configurations added

Workflow updates and standardized pre-commit changes and configurations added #3

Triggered via pull request February 26, 2025 23:15
Status Failure
Total duration 15m 58s
Artifacts 1

call-push.yml

on: pull_request
call-push  /  compile
36s
call-push / compile
call-push  /  pre-commit
2m 33s
call-push / pre-commit
call-push  /  security-scans
1m 26s
call-push / security-scans
call-push  /  test-coverage
7s
call-push / test-coverage
call-push  /  build
19s
call-push / build
call-push  /  test-setup
3s
call-push / test-setup
call-push  /  integration-test
42s
call-push / integration-test
Matrix: call-push / sanity-test
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 1 warning
call-push / integration-test
Process completed with exit code 1.
call-push / sanity-test (current, 10.1.65.241)
Process completed with exit code 1.
call-push / sanity-test (previous, 10.1.18.235)
Process completed with exit code 1.
call-push / sanity-test (next, 10.1.66.104)
Process completed with exit code 1.
call-push / sanity-test (rhel, 10.1.19.212)
Process completed with exit code 1.
call-push / sanity-test (cloud, ssc-cicd-sanity-tests.soar.stg.splunkcloud.com)
The self-hosted runner: 447a6a34-7731-46e4-9d2f-46b33fdca274 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.
call-push / pre-commit
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

Artifacts

Produced during runtime
Name Size
app-tar
21.4 KB