Repository navigation
test(computer): the framework-only routes test sends from a pinned image, and docker's errors say why - #732
Merged
earakely-scale merged 2 commits intoNov 17, 2026
Conversation
…age, and docker's errors say why The test's request from another container ran an unpinned public.ecr.aws python image, and docker run exited 125 before the request on main's CI four times recently, the last keeping v0.9.1551 off PyPI. It now runs the digest-pinned mirror.gcr.io image the test Dockerfiles use, and the computer tests' docker helper adds docker's stderr to its error. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
earakely-scale
deleted the
edgararakelyan/computer-env-test-pinned-python
branch
November 17, 2026 05:34
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.
Why
main's CI failed on the v0.9.1551 bump commit, so that release didn't publish either. This time the failure wasintegration-local-slow (8/12):The same test failed the same way, exit status 125, in 4 of the last 15 failed
local-backendsruns: 43954413405, 43970572534, 43982081157 and 44018886899. Exit 125 meansdocker runitself failed, before the container ran. The test sends its request from a container of an unpinnedpublic.ecr.awsimage that is pulled at that moment, so most likely the pull failed. The run doesn't say: the helper captures docker's stderr, andCalledProcessErrordoesn't print it.What changes
mirror.gcr.io/library/python:3.12-slim, pinned by digest. It's the image every test Dockerfile intst/datauses, and other integration tests pin it the same way (vm_sandbox_build_test.py,prune_test.py).docker()helper adds docker's stderr to theCalledProcessErroras a note, so a failed docker call says why in the test report.Tests only.
Testing
ruff checkpasses. The test runs inintegration-local-slow.🤖 Generated with Claude Code


Confidence Score: 5/5
The PR appears safe to merge.Summary
The test now sends its container request from a digest-pinned Python image. Failed Docker calls include the last 2000 characters of stderr.
Reviews (2) · Last reviewed commit: "test(computer): name how much of docker'..." · Reviewed by Greptile