test: harden database qualification startup and cleanup evidence

2026-10-24 14:04:57 +02:00
parent 2b26953d6f
commit 5ac11549b2
16 changed files with 228 additions and 15 deletions
@@ -42,3 +42,13 @@ Do not remove the blocker merely because Docker becomes available. Under the obs
 The current fixture and `--existing-server` runner deliberately allow only explicit loopback TCP. A later private service transport must preserve those defaults and receive separately reviewed narrow endpoint validation; no fixture bypass is included here.

 Sanitized API metadata, source/log hashes, precise blockers and next actions are in [ci-findings.json](ci-findings.json) and [CI_OPERATOR_HANDOFF.md](CI_OPERATOR_HANDOFF.md). Ignored raw files remain local; no credentials or full environment/configuration are copied into these tracked reports.
+
+## Source checkpoint recheck
+
+Run849/job1739 at `1a1b7c82213c24fbbc9bd4e1553a92f4c76eabd9` was inspected at11:24:57UTC.
+Runner5 `Live-Runner` again prepares a host-network job with the existing merged Docker socket
+bind. The first isolation guard exits1; no MariaDB test executes. The API marks downstream steps
+as failed, while the raw log explicitly says the checkout/setup main steps were skipped.
+The raw log SHA-256 is `4aeee7452db935ecf01afad44d2812e7fb9160239317c87d6a3d429cbdd128de`.
+This independently confirms the same **BLOCKED** disposition at the published harness checkpoint;
+it is neither a hosted MariaDB PASS nor an executed database-test failure.