ci: investigate test failures on main since Python 3.14 bump #15

New issue

Closed

opened 2026-05-03 14:56:23 +00:00 by gravityfargo · 1 comment

gravityfargo commented

2026-05-03 14:56:23 +00:00

Owner

Context

Test runs on main have failed for the last 4 commits (since the Python 3.14 + dev-env-sync merge):

#11 chore: bump to Python 3.14 + sync dev-env standards
#12 feat: file ops helpers for archive coupling

Local `make test` passes (247 tests). Failures are CI-only.

Possible causes

`astral-sh/setup-uv@v7` may not provision Python 3.14 in CI runners (the runner image may need updating, or uv-managed Python pin in pyproject)
Cached test media (NASA / Capital PDF) downloaded by `actions/cache@v4` may be stale or incompatible
`uv run --frozen pytest` may differ from local `make test` invocation

Notes

CI logs are auth-walled via `fj actions`; investigation will need the web UI or direct runner access.

Acceptance criteria

Root cause identified
Main CI back to green
Document the fix in CLAUDE.md if it's an environmental gotcha

## Context Test runs on main have failed for the last 4 commits (since the Python 3.14 + dev-env-sync merge): - #11 chore: bump to Python 3.14 + sync dev-env standards - #12 feat: file ops helpers for archive coupling Local \`make test\` passes (247 tests). Failures are CI-only. ## Possible causes - \`astral-sh/setup-uv@v7\` may not provision Python 3.14 in CI runners (the runner image may need updating, or uv-managed Python pin in pyproject) - Cached test media (NASA / Capital PDF) downloaded by \`actions/cache@v4\` may be stale or incompatible - \`uv run --frozen pytest\` may differ from local \`make test\` invocation ## Notes CI logs are auth-walled via \`fj actions\`; investigation will need the web UI or direct runner access. ## Acceptance criteria - [ ] Root cause identified - [ ] Main CI back to green - [ ] Document the fix in CLAUDE.md if it's an environmental gotcha

gravityfargo added the

bug

label

2026-05-03 14:56:30 +00:00

gravityfargo referenced this issue from a commit

2026-05-03 16:53:49 +00:00

ci: run pytest inside athena-archive-ci container

gravityfargo referenced this issue from a pull request that will close it,

2026-05-03 16:54:04 +00:00

ci: run pytest inside athena-archive-ci container #20

gravityfargo commented

2026-05-03 16:56:25 +00:00

Author

Owner

PR #20 attempted to fix this by adding container: to the workflow but no CI tasks fired (silent skip — likely runner doesn't support container jobs, or YAML parse fail). Without CI log access I can't narrow it further. Closing #20; #15 remains open for someone with web/runner access to investigate.

PR #20 attempted to fix this by adding `container:` to the workflow but no CI tasks fired (silent skip — likely runner doesn't support container jobs, or YAML parse fail). Without CI log access I can't narrow it further. Closing #20; #15 remains open for someone with web/runner access to investigate.

gravityfargo referenced this issue from a commit

2026-05-03 17:08:20 +00:00

ci: replace per-step setup with Dockerfile.test container

gravityfargo referenced this issue from a pull request that will close it,

2026-05-03 17:08:45 +00:00

chore: containerize tests + fix CI workflow #21

gravityfargo referenced this issue from a commit

2026-05-03 17:22:25 +00:00

ci: bundle external test fixtures into Dockerfile.test

gravityfargo closed this issue

2026-05-03 17:31:53 +00:00

gravityfargo referenced this issue from a commit