fix: run django case study via django's own CI steps; formalize cache policy#5
Open
ozeranskii wants to merge 2 commits into
Open
fix: run django case study via django's own CI steps; formalize cache policy#5ozeranskii wants to merge 2 commits into
ozeranskii wants to merge 2 commits into
Conversation
…hed-dev) django 6.0.6 ships no uv.lock; its Linux CI (python_matrix.yml) runs the suite via pip + runtests.py and installs libmemcached-dev itself, because pylibmc has no wheels for Python 3.12+ and the runner images don't bundle the headers. Replicate those exact steps (identical on both runners) instead of the earlier uv/tox attempt (which was flask's pattern and fails on django for lack of a lockfile).
Define the headline comparison as cold-cold (cache-neutral workflow; the GitHub side is cold by construction, the self-hosted side's transparent dependency cache cleared before each cold run) — it isolates the runner with no caching asymmetry. Warm stays a separately-labelled steady-state row (each platform's native cache primed), never compared against cold.
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
1 participant
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 django case study now runs django's own Linux CI steps (their
python_matrix.yml): installlibmemcached-dev(pylibmc has no wheels for Python 3.12+ and the runner images don't bundle the headers, so django installs them itself), thenpip install -r tests/requirements/py3.txt -e .andpython -Wall tests/runtests.py -v2. The earlieruv run --locked toxattempt was flask's pattern and fails on django (no lockfile at this pin).Validated green on
ubuntu-latest: 18710 tests, ~233s suite (299s job). A one-off failure on the first try was django's own flakysignals.SignalTests.test_delete_signals; a re-run passed.Also formalizes the cache policy in
methodology.md: cold-cold is the canonical headline (cache-neutral workflow; GitHub side cold by construction, self-hosted transparent dependency cache cleared before each cold run); warm is a separately-labelled steady-state row, never compared against cold.