Skip to content

Fix the Python tests on Linux: regenerate managed locks per machine - #78

Merged
rmichaelthomas merged 1 commit into
mainfrom
ci-python-tests-linux
Nov 16, 2026
Merged

rmichaelthomas merged 1 commit into
mainfrom
ci-python-tests-linux

Conversation

@rmichaelthomas

Copy link
Copy Markdown
Owner

The new main-branch Python step ran on the Ubuntu runner for the first time (run 43810923927): 145 of 157 tests passed; the 12 that failed were the managed-Python tests in test_feed_digest and test_feed_inbox, all with "managed Python lock does not match this target". The committed locks name macos-aarch64.

The tests now run guion sync --update in their working copy, so they do not depend on the machine that made the lock. Verified locally with the committed locks pointed at linux-x86_64 (12/12 pass) and unchanged (12/12 pass).

Until this merges, main's source-checks job fails on that step.

🤖 Generated with Claude Code

The committed locks name macos-aarch64, so on the Linux runner all 12 managed-Python
tests failed with a lock mismatch. They now run guion sync --update in their copy.
Verified by pointing the committed locks at linux-x86_64 locally.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@rmichaelthomas
rmichaelthomas merged commit d5a3bbc into main Nov 16, 2026
4 checks passed
@rmichaelthomas
rmichaelthomas deleted the ci-python-tests-linux branch November 16, 2026 05:56
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