Repository navigation
CI: run on a self-hosted runner on dev-01 - #71
Merged
Merged
Conversation
Hosted minutes ran out. Every job runs on [self-hosted, linux, dev-01], a shared host whose own Compose stack holds :8080, :8000 and 127.0.0.1:5432, so no job maps a fixed host port or installs host packages: - api runs in python:3.12 (setup-python has no builds for Debian 13) with postgres, mongo and the MLflow server as services reached by name. - stack runs its own Compose project on ephemeral loopback ports, Playwright in its image, and removes the stack, volumes and images after. - lint runs ruff from Astral's image of the pinned version; images tags its builds under a CI project name and removes them after. - Container jobs hand the workspace back to the runner's user; host jobs reclaim it first. - Pull requests only: no badge reads main's runs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LqNnEU86Q4fmrJnN2rXovS
dev-01's Docker gives containers a soft nofile of 1024; the API suite's collections exhausted it and WiredTiger panicked. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LqNnEU86Q4fmrJnN2rXovS
The URI-redaction tests assert the store's host name never appears in an error; with the host named mongo, the connection's own name (mongo-<id>) matched it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LqNnEU86Q4fmrJnN2rXovS
systemd-resolved on dev-01 takes 12-15 s to fail a single-label name over LLMNR; the own-address guard's lookups of the Compose names give up after 2 s, so the guard tests depended on timing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LqNnEU86Q4fmrJnN2rXovS
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The repo is out of hosted Actions minutes, so CI moves to a self-hosted runner on dev-01 (registered to this repo only, labels
self-hosted, Linux, X64, dev-01).dev-01 is shared: its own Compose stack holds :8080, :8000 and 127.0.0.1:5432, and other sessions run containers there. So no job maps a fixed host port or installs host packages (no sudo):
python:3.12(setup-python has no builds for dev-01's Debian 13). Postgres, Mongo and the MLflow tracking server are services reached by name (postgres,mongo,mlflow), with no host ports. The MLflow server is now a service container rather than adocker run -p 5000:5000. The pip cache is a named volume.rf-ci-stack-<runner>) on ephemeral loopback ports. Playwright runs in its image as the runner's user. The stack, its volumes and its images are removed afterwards, and any stack an earlier run left behind is removed first.requirements-dev.txt.sudo apt-get install gettext-basestep, because envsubst is already on dev-01.rf-ci-images-<runner>-*, so they never retag the images dev-01's stack runs. The tags are removed afterwards, and the layers stay in the build cache.pull_requestonly. No badge reads main's runs, and a merge has already passed as a PR.concurrency: cancel-in-progressis kept.🤖 Generated with Claude Code
https://claude.ai/code/session_01LqNnEU86Q4fmrJnN2rXovS