Skip to content
This repository has been archived by the owner on Nov 25, 2022. It is now read-only.

Run some of the synapse tests against python 3.8/postgres 12 #29

Merged
merged 1 commit into from
Jan 10, 2020

Conversation

richvdh
Copy link
Member

@richvdh richvdh commented Jan 9, 2020

No description provided.

@richvdh richvdh requested a review from erikjohnston January 9, 2020 18:26
Copy link
Member

@erikjohnston erikjohnston left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Its fine, what's the rationale for the other bits of shuffling ooi?

@@ -183,7 +189,7 @@ steps:
- exit_status: 2
limit: 2

- label: ":python: 3.7 / :postgres: 9.5"
- label: ":python: 3.7 / :postgres: 11"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this change? Why are we testing pg11?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Github isn't doing the best job of showing a sensible diff.

I was thinking it would be sensible to test against a range of postgres versions rather than just min and max, hence I'm suggesting we retain the current tests against py3.7/pg11.

Rather, I'm replacing the tests against py3.7/pg9.5 with tests against py3.8/pg12; the rationale being that we already testing against pg9.5 (in the py3.5/pg9.5 tests), and I'm not super-keen to introduce even more test runs.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ooooh, right yes. Agreed.

@richvdh richvdh merged commit e4bace2 into master Jan 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants