mosaicstack/stack
1
0
Fork 1
Code Issues 177 Pull Requests 9 Actions Packages Projects Releases 15 Wiki Activity

test(ci): correct RM-61 crash control entrypoint
ci/woodpecker/pr/ci Pipeline failed
Details

Browse Source
This commit is contained in:
coder-mos1
2026-08-01 08:28:30 -05:00
parent 9455cd6a26
commit 25ac59715a
2 changed files with 10 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.woodpecker/ci.yml
+1 -1
View File
@@ -148,10 +148,10 @@ services:
POSTGRES_USER: mosaic POSTGRES_USER: mosaic
POSTGRES_PASSWORD: mosaic POSTGRES_PASSWORD: mosaic
POSTGRES_DB: mosaic POSTGRES_DB: mosaic
PGPASSWORD: mosaic
entrypoint: entrypoint:
- /bin/sh - /bin/sh
- -c - -c
commands:
- | - |
docker-entrypoint.sh postgres & docker-entrypoint.sh postgres &
postgres_pid=$$! postgres_pid=$$!
docs/scratchpads/1000-rm-61-ci-contract-exemption.md
+9
View File
@@ -51,6 +51,15 @@ Historical JSON saved locally under `.evidence/rm-61/` (not for commit). Supplie
This control is red and its service record differs from #1000 (`exit_code=0` plus pod-not-found). It proves the startup-failure direction only. It does not settle the dangerous post-readiness crash/garbage-collection path. This control is red and its service record differs from #1000 (`exit_code=0` plus pod-not-found). It proves the startup-failure direction only. It does not settle the dangerous post-readiness crash/garbage-collection path.
### Control 2 setup attempt — invalid, excluded from evidence
- Commit: `9455cd6a2650b2b7e70f746c07933d96e5cb3d20`
- Pipeline: #2190, exact commit match.
- Full JSON child scan: 9 total — 7 success, 2 failure, 0 skipped/pending/running.
- Service log: `/bin/sh: 0: -c requires an argument`.
- Root cause: Woodpecker service `commands` did not become the third `sh -c` argument. PostgreSQL never started, so this run is **not** the post-readiness crash control and provides no discrimination evidence.
- Focused remediation: place the script directly in the third `entrypoint` element and supply `PGPASSWORD` for the marker query. This is a control-fixture correction, not a retry of #1000 and not evidence for either verdict.
## Risks ## Risks
The Woodpecker Kubernetes backend may garbage-collect both genuinely failed and successfully used service pods before reconciliation. If so, the provider-visible service signature cannot safely support Option B. The Woodpecker Kubernetes backend may garbage-collect both genuinely failed and successfully used service pods before reconciliation. If so, the provider-visible service signature cannot safely support Option B.