Skip to content

ci: run the local Python regression suites - #8

Draft
mptfire wants to merge 1 commit into
masterfrom
ci/python-regressions
Draft

mptfire wants to merge 1 commit into
masterfrom
ci/python-regressions

Conversation

@mptfire

@mptfire mptfire commented Oct 13, 2026

Copy link
Copy Markdown
Owner

Published as a draft for owner review.

Problem

tests/test_apkdiff.py (AMB-008) and tests/test_release_workflow.py (AMB-010) ship with the fix branches but no CI job executes them — their regression value was zero by default, and the AMB-010 PR body already had to disclose "the test is local and is not automatically wired into existing CI."

Fix

New Python regressions workflow: python3 -m unittest discover -s tests -v whenever a tests/ directory exists, no-op (green) on branches without one. Triggered on pull_request → master and push → master, matching check-offline-permissions.yml's shape; contents: read only; 5-minute timeout.

Once AMB-008 and AMB-010 merge to master, every later PR — including their own follow-ups — runs both suites automatically.

Validation

Self-evident from the YAML; the suites themselves pass locally (see apkdiff-patched.log / release-tag-patched.log in the local evidence package) and will run on this branch's CI as a trivial no-op until tests/ lands.

tests/test_apkdiff.py and tests/test_release_workflow.py were added with
no CI job, so their regression value was zero by default. Run unittest
discover when tests/ exists; keep the job green on branches without it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant