Repository navigation
fix: gate signing intake before quorum retrieval #8418
Triggered via pull request
October 8, 2026 23:58
PastaPastaPasta
PastaPastaPasta
synchronize
#7833
Status
Success
Total duration
1h 24m 30s
Artifacts
–
build.yml
on: pull_request_target
Check skip conditions
29s
Build slim container
/
Build container (amd64)
0s
Build slim container
/
Build container (arm64)
0s
Build container
/
Build container (amd64)
0s
Build container
/
Build container (arm64)
0s
Build slim container
/
Create multi-arch manifest
0s
aarch64-linux-build
/
Build source
3m 4s
linux64_fuzz-build
/
Build source
4m 23s
mac-build
/
Build source
4m 22s
win64-build
/
Build source
7m 5s
linux64-test
/
Test source
21m 36s
linux64_asan-test
/
Test source
30m 11s
linux64_sqlite-test
/
Test source
19m 57s
linux64_tsan-test
/
Test source
43m 5s
linux64_multiprocess-test
/
Test source
37m 48s
linux64_nowallet-test
/
Test source
7m 29s
Annotations
1 warning and 2 notices
|
Workflow execution policy warning (evaluate mode):
.github/workflows/build.yml#L1
On November 2, 2026, GitHub will restrict `pull_request_target` on public repositories by default. To continue allowing the event trigger, configure an Actions policy. Learn more: https://gh.io/securely-using-pull_request_target#default-policy-for-pull_request_target
|
|
dashcore-ci-slim
Using existing container ghcr.io/dashpay/dash/dashcore-ci-slim@sha256:3e7e1d24e69800822027af2fd25e0697f80e6591c40a7b69d6782f69761c36f4, build skipped
|
|
dashcore-ci-runner
Using existing container ghcr.io/dashpay/dash/dashcore-ci-runner@sha256:86bfa0cae9471ee5ca32c0746e1f175c7777740d8396683de750577a5db60973, build skipped
|