-
Notifications
You must be signed in to change notification settings - Fork 29
test with postgres 16.4 #6063
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test with postgres 16.4 #6063
Conversation
Hmmm, no 16.6 image. May need to consider 17.0, but they also seem to be missing 17.1 and 17.2 Edit to add: |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #6063 +/- ##
==========================================
Coverage 74.41% 74.41%
- Complexity 5632 5633 +1
==========================================
Files 386 386
Lines 20192 20192
Branches 2085 2085
==========================================
+ Hits 15025 15026 +1
Misses 4167 4167
+ Partials 1000 999 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
This reverts commit dd9a44e.
|
Actually, I'm going to have to backport this to a hotfix, but will still merge this into develop |
Description
Switch tests to postgres 16.4. Will be followed by changes to dockstore-deploy and test deployments on qa, staging, prod.
Review Instructions
I tested the DB doc build and ran docker compose as well as the tests themselves. Could probably do the first two.
Issue
https://ucsc-cgl.atlassian.net/browse/SEAB-6853
https://ucsc-cgl.atlassian.net/browse/SEAB-6875
Security and Privacy
None, this should address the linked tickets though
Please make sure that you've checked the following before submitting your pull request. Thanks!
mvn clean install
@RolesAllowed
annotation