ci: update test automation to run PG17 #72
Merged
Conversation
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
Upstream nixpkgs separated out pg_config into a separate development tool package, rather than being part of the std. PostgreSQL package. However, installing a PG extension is only part of the std PostgreSQL package, so we can't get a pg_config that references a PG with extensions preconfigured. To fix this, reorder the package builds so that we build up from the Python module first and assemble the PostgreSQL package last.
mfenniak
changed the title
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.
Updates test automation to run successfully on PostgreSQL 17. Updates all PostgreSQL & Python versions under test to their latest minor releases, as well. Disables test automation for Python 3.9 (due to upcoming EOL) and Python 3.10 (due to conflict w/ Sphinx python requirements, which is a transitive dependency of the sqlalchemy package).
After an initial revision wasn't actually running tests and was silently succeeding, some additional tweaks to ensure that tests have run and have successful output were added as well.