docs(ci): record hosted MariaDB runner prerequisite failure
MariaDB persistence qualification / mariadb (push) Failing after 46s
MariaDB persistence qualification / mariadb (push) Failing after 46s
This commit is contained in:
@@ -16,7 +16,7 @@ See [machine-readable validation](validation.json), [setup](README.md), and [run
|
||||
| --- | --- | --- |
|
||||
| MariaDB 12.2.2 RD21 qualification | **PASS, bounded resolution** | 32 real-provider cases and one native browser journey; durable SQL state, transactions, rejected drafts, revision conflicts, recovery and tenant isolation. No production image equality claim. |
|
||||
| MariaDB local development | **READY** | Pinned Compose image, healthy loopback service, separate persistent development volume, API startup applies 51 migrations; synthetic company survives database stop/start. |
|
||||
| MariaDB CI/integration tests | **LOCAL READY; HOSTED UNVERIFIED** | Same fail-closed runner passes 32/32 using Docker, locked restore, isolated tmpfs and generated schemas. Workflow added; no successful hosted run claimed. Runner must provide Docker/Compose and .NET 9.0.317. |
|
||||
| MariaDB CI/integration tests | **LOCAL READY; HOSTED BLOCKED** | Same fail-closed runner passes 32/32 locally. Hosted run843 passed checkout/SDK setup/five runner guards, then failed `Require Docker and Compose`: `docker: command not found`, exit127. No hosted MariaDB tests ran. A dedicated test runner needs Docker/Compose and an isolated engine. |
|
||||
| Historical fixture repairs | **PASS** | Three obsolete revision fixtures corrected without weakening assertions: diagnostics 18/18, volume 3/3. Stale writes now assert 409 and preservation of the winner/source/history. |
|
||||
| SQLite retirement | **PLAN READY; REMOVAL NO-GO** | Complete baseline classification; defaults corrected. Remaining legacy coverage, full-fidelity transfer and preservation/restore gates must precede package/branch removal. |
|
||||
| MariaDB 12.3 LTS migration | **INVESTIGATION READY; MIGRATION NO-GO** | Separate 12.3.3 rehearsal proposed; target image/driver certification, copied-data upgrade, backup/restore and rollback-after-writes remain untested. |
|
||||
@@ -76,6 +76,14 @@ now uses the existing bridge network, avoiding leaked per-run networks. Final re
|
||||
actionable findings. Docker's local stale socket issue was also resolved without resetting Docker
|
||||
or deleting its persistent data; see [local recovery](DOCKER_LOCAL_RECOVERY.md).
|
||||
|
||||
Authenticated hosted verification: [run843](https://git.cesnimda.uk/cesnimda/jobtrackingapp/actions/runs/843)
|
||||
at report commit `e75c4a477555bbd360b83004c25c30fbfcf233d3` failed the explicit Docker prerequisite.
|
||||
The Gitea step API labels earlier steps as failed too; the actual job log confirms checkout, SDK
|
||||
installation and five guard cases succeeded. No database tests or database artifacts were produced.
|
||||
Do not bypass the gate with SQLite, attach a production host socket, or silently grant runner
|
||||
privileges. Provision an isolated CI database execution environment, rerun the same command and
|
||||
verify the actual TRX/cleanup evidence before changing hosted readiness to PASS.
|
||||
|
||||
The intended final architecture is **MariaDB only** for application development, integration,
|
||||
CI and production. Keep 12.2.2 pinned for the present qualification; rehearse the supported 12.3 LTS
|
||||
path separately using [the migration gates](MARIADB_12_3_PLAN.md). Retire SQLite in the documented
|
||||
|
||||
Reference in New Issue
Block a user