ci: add Python 3.14 test lane exercising the 3.14 compatibility surface - #54
Closed
spfcraze wants to merge 1 commit into
Closed
ci: add Python 3.14 test lane exercising the 3.14 compatibility surface#54spfcraze wants to merge 1 commit into
spfcraze wants to merge 1 commit into
Conversation
spfcraze
force-pushed
the
feat/ci-py314-lane
branch
from
August 10, 2026 19:57
dddc27e to
4749eb3
Compare
૮ >ﻌ< ა ci reviewran on 4749eb3 — ci: add Python 3.14 test lane exercising the 3.14 compatibil ❌ Job failuresPython tests / test-py314 · View jobJob Python tests / test-py314 failed.
|
Owner
Author
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.
ci: add Python 3.14 test lane
Summary
Adds a
test-py314job to.github/workflows/tests.ymlthat exercises thePython 3.14 compatibility surface on a supported CI interpreter. The
project's CI is currently 3.11-only (
uv python install 3.11/uv sync --locked --python 3.11in both test jobs); the 3.14 support work(daemon_pool WorkerContext, wake-word ai-edge-litert bridge, stdlib
removals) has no CI coverage.
This addresses the gap noted in sweeper reviews of the daemon_pool 3.14
work: the project's
requires-pythonwas capped below 3.14, so the3.14-specific tests could not exercise
_create_worker_contexton asupported CI interpreter. Once the ceiling is raised, this lane is what
actually verifies the 3.14 surface on every PR.
What the lane runs
uv sync --locked --python 3.14 --extra all --extra dev --extra wake— the same pinned lockfile, resolved for 3.14 (cp314 wheels verified for
the full dependency set;
tflite-runtimeis excluded on 3.12+ via themarker-gated override in
pyproject.toml).tests/tools/test_daemon_pool.py(WorkerContext)tests/tools/test_wake_word.py(ai-edge-litert bridge)tests/tools/test_delegate.py(depends on the daemon pool timeout executor)tests/tools/test_async_delegation.pytests/agent/test_compression_concurrent_fork.pyindependently of the 3.11 lane and the duration-cache merge.
Verification (this machine, Python 3.14.4, the exact lane command)
Why this is additive
The open daemon_pool 3.14 PRs all modify
tools/daemon_pool.py; nonetouches
.github/workflows/. This PR is CI-only — it makes all of thosefixes verifiable, and is independent of which daemon_pool implementation
lands.
Notes
requires-pythonto accept 3.14 (the ceiling raise is handledby the separate 3.14-support PRs). The lane installs with
--lockedagainst the current lockfile; until the ceiling is raised the lane will
need the lockfile's 3.14 markers (already present in
uv.lock).test-py314is intentionally bounded (5 files) to keep CI time incheck; it can be expanded to the full slice matrix once 3.14 is the
supported default.