Rebuild cached omc/OMSimulator that do not run in the image - #339
Merged
Conversation
Since the jobs moved into a container, a cache keyed on the git hash alone restores binaries built on the node: the maintenance branches have not moved, so v1.26 and v1.27 got a node-built omc that cannot load inside the image and died as exit code 127 out of test.py. Check that the restored build runs and rebuild it if it does not, for omc and for OMSimulator. Also run clean-empty-omcversion-dates.py in the image: it needs psycopg2, which is in the image's python environment and not on the node. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
AnHeuermann
marked this pull request as ready for review
August 27, 2026 14:11
AnHeuermann
enabled auto-merge (squash)
August 27, 2026 14:11
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.
Issue
#335 broke the library testing.
Jenkins reports errors in the master stage like:
The maintenance branches reports errors like:
Changes
Since the jobs moved into a container, a cache keyed on the git hash alone restores binaries built on the node: the maintenance branches have not moved, so v1.26 and v1.27 got a node-built omc that cannot load inside the image and died as exit code 127 out of test.py. Check that the restored build runs and rebuild it if it does not, for omc and for OMSimulator.
Also run clean-empty-omcversion-dates.py in the image: it needs psycopg2, which is in the image's python environment and not on the node.