-
Notifications
You must be signed in to change notification settings - Fork 11
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: Run Postgres tests with version 14 15 16 #367
base: main
Are you sure you want to change the base?
Conversation
It seems some Postgres only tests are flaky like admin-service.test.js (example) |
@@ -3,7 +3,7 @@ version: '3.1' | |||
|
|||
services: | |||
db: | |||
image: postgres:16-alpine | |||
image: postgres:${VER}-alpine |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would always require you to set the env variable locally as well. I'd prefer a solution that works locally ootb.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have adjusted npm run start
to always include the latest as default value.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sounds good to me. Could you please check the failing pipeline as well?
In general, I don't think it's required to run all versions on each PR. A cron job doing this nightly is imo sufficient. |
As requested by #364