Repository navigation
Build PyMEOS-CFFI from the branch of the MEOS line the version maps to - #103
Merged
estebanzimanyi merged 1 commit intoOct 22, 2026
Conversation
The test job builds MEOS from the MobilityDB branch the package version maps to (stable-X.Y on a released line, master on the next one), and PyMEOS-CFFI from a branch named as the PyMEOS one or else from the same line: the PyMEOS-CFFI stable-1.3 branch for 1.3.x, master for 1.4. Witness: PyMEOS MobilityDB#56 (run 39871461408) builds MEOS from stable-1.3 and, finding no PyMEOS-CFFI branch named gaps, clones PyMEOS-CFFI master, the 1.4 line, whose generator reads a catalog the 1.3 job does not provide: every job fails at "Install pymeos_cffi" with FileNotFoundError: builder/meos-idl.json. Measured: on the released stack (pymeos-cffi 1.3.0), PyMEOS master passes 4462 tests and MobilityDB#56 4505, the same 24 MF-JSON whitespace failures on both. Why: a released PyMEOS line binds the released MEOS line and the CFFI cut from it; CFFI master tracks MEOS master, so it never builds against a stable-X.Y libmeos.
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.
The test job builds MEOS from the MobilityDB branch the package version maps to (stable-X.Y on a released line, master on the next one), and PyMEOS-CFFI from a branch named as the PyMEOS one or else from the same line: the PyMEOS-CFFI
stable-1.3branch for 1.3.x,masterfor 1.4.Witness: PyMEOS #56 (run 39871461408) builds MEOS from
stable-1.3and, finding no PyMEOS-CFFI branch namedgaps, clones PyMEOS-CFFImaster, the 1.4 line, whose generator reads a catalog the 1.3 job does not provide: every job fails at "Install pymeos_cffi" withFileNotFoundError: builder/meos-idl.json.Measured: on the released stack (pymeos-cffi 1.3.0), PyMEOS master passes 4462 tests and #56 4505, the same 24 MF-JSON whitespace failures on both.
Why: a released PyMEOS line binds the released MEOS line and the CFFI cut from it; PyMEOS-CFFI
mastertracks MEOS master, so it never builds against astable-X.Ylibmeos.