Repository navigation
Give each start-point create its own build tag - #41
Merged
Merged
Conversation
Every create built to one fixed tag, cyberdojo/temporary_start_points, and then tagged it to the name asked for. Two creates at once meant the second build took the tag from the first, which then shipped an image holding the other start-point, under its own name and with no error anywhere. Seen while making the start-point traffic-light tests runnable in parallel: a run of bash-shunit2 was served bash-unit files and scored 33 failures. RAND was already computed for the check container name, so the tag now carries it too. Five concurrent pairs pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Every create built to one fixed tag,
cyberdojo/temporary_start_points, and
then tagged it to the name asked for.
Two creates at once meant the second
build took the tag from the first, which
then shipped an image holding the other
start-point, under its own name and with
no error anywhere.
Seen while making the start-point
traffic-light tests runnable in parallel:
a run of bash-shunit2 was served
bash-unit files and scored 33 failures.
RAND was already computed for the check
container name, so the tag now carries
it too. Five concurrent pairs pass.