Skip to content

Latest commit

 

History

History
99 lines (81 loc) · 4.84 KB

factorize-validation-runner.md

File metadata and controls

99 lines (81 loc) · 4.84 KB

Factorize validation runner image

The Factorize-specific exe.dev runner image is built from Dockerfile.validation-runner, using the documented exe.dev exeuntu base. It keeps the base image's SSH, systemd, exedev user, and agent setup while adding prerequisites for the complete Factorize test suite.

The image pins Node 24.12.0, npm 11.19.0, and Playwright/Chromium 1.64.0. It installs PostgreSQL 16 without starting systemd during image build, enables the PostgreSQL service for VM boot, and sets the postgres password used by scripts/bootstrap-test.mjs. PostgreSQL listens on loopback; the test bootstrap creates and recreates only its isolated validation database. The image sets PLAYWRIGHT_BROWSERS_PATH=/opt/ms-playwright as an OCI environment variable so non-login job processes inherit the installed browser location. The Docker build launches Chromium as exedev; the post-boot smoke command also checks password authentication over TCP and Chromium from the job user.

Build, publish, and pin

The build/publish script uses the attached GHCR integration and prints the immutable public image reference with its registry digest:

scripts/build-validation-runner-image.sh

The resulting package must be public because exe.dev job images are pulled by the host and private images are unsupported for jobs. Set the Factorize Dev job's image to the printed ghcr.io/generationsoftware/factorize-validation-runner@sha256:… reference, preserving its other execution configuration. Do not use a mutable tag for the job image. Record the exact digest in the issue handoff and validation record below.

Fresh-VM acceptance

After booting the pinned image, run the image smoke check, then check out the Factorize repository and run the full local validation:

scripts/smoke-validation-runner-image.sh
npm ci
npm run test:local

test:local resets the local validation database, applies the migrations from that checkout, sets all three isolated database URLs in the root test process, and runs npm test. Before it drops or recreates the database, test:local launches Chromium and authenticates to the configured local PostgreSQL admin URL, so missing image prerequisites fail before migrations or the full suite. A failure requires correcting the image or bootstrap and publishing a new digest, followed by repeating this sequence.

Background run acceptance

npm run test:local includes the background run acceptance scenario. It starts the Worker and PostgreSQL locally. A deterministic VM backend receives the scheduler's launch requests and supplies success and failure responses. The test dispatches through MCP, listens for a resource update, and delivers each terminal outcome to a durable conversation inbox. It also exercises vendor identity, duplicate submissions, capacity, cancellation, replay, and run history after template deletion. Chromium covers the launch form and skill filter in the browser lane.

For a focused rerun after npm ci, run npm run bootstrap:test, export the local database variables it prints, then run:

npm run build --workspace=factorize-app
node --test scripts/agent-api-runtime.test.mjs
node --test --test-name-pattern='filter direct runs' packages/app/test/runs.browser.test.mjs

The host adapter accepts an authenticated MCP request function, a conversation ID, and an idempotent delivery callback. The acceptance test supplies a PostgreSQL inbox and verifies delivery after reconnecting.

Validated image record

Field Value
Public image digest ghcr.io/generationsoftware/factorize-validation-runner@sha256:1333c4a7bb49c4cbcdd28ca2b57331dfcbff7cf611db1aaeaa4830517aacf6d4
Node / npm / Playwright 24.12.0 / 11.19.0 / 1.64.0
Image smoke and full suite Passed in a Docker container pulled anonymously from the immutable digest; not fresh-VM evidence
Fresh Dev VM and Dev job image pin Pending; keep PR #392 draft and GEN-2889 In Progress until this gate passes

The checkpoint pull and container validation were repeated on 2026-11-11. An unauthenticated GHCR manifest request returned HTTP 200 for the digest, and docker pull with an empty Docker config downloaded the same digest. In a container from that image, the PostgreSQL authentication helper and image smoke passed, followed by npm ci and npm run test:local on Factorize commit 02f96e9e23908537fffc2584b26abe85c34b1090 (backend 569 passed / 5 skipped, browser 102 passed / 1 skipped, proxy checks and builds passed). The container test starts PostgreSQL and invokes the image's authentication helper as setup; it does not verify exe.dev VM boot behavior. The Dev job remains on ghcr.io/generationsoftware/anarack:latest. A fresh Dev VM must still boot from the digest and pass these checks before the job image is pinned.