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

Update Synapse pipelines for Python 3.9 #119

Merged
merged 11 commits into from
Jan 8, 2021
Merged

Update Synapse pipelines for Python 3.9 #119

Changes from 3 commits
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
4972748
Define what we want to test
callahad Jan 7, 2021
41b6332
Remove commented-out and unused coveralls plugin
callahad Jan 7, 2021
e4c196e
Re-order tests to run special cases first
callahad Jan 7, 2021
9a20e66
Test against Python 3.9
callahad Jan 7, 2021
88cc127
Update tested versions of Python + Postgres
callahad Jan 7, 2021
8daf3ca
Bump Python and Pg versions for synapse_port_db
callahad Jan 7, 2021
48def3e
State what we're trying to test with Sytest
callahad Jan 7, 2021
479b21e
Make labels for build steps more compact
callahad Jan 7, 2021
ad6053c
Fix label typo
callahad Jan 8, 2021
ed3a4ad
Enumerate Debian versions in comments
callahad Jan 8, 2021
5825a83
Add note about MULTI_POSTGRES
callahad Jan 8, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 10 additions & 7 deletions synapse/pipeline.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -288,24 +288,27 @@ steps:
#
# Our tests have three dimensions:
# 1. Topology (Monolith, Workers, Workers w/ Redis)
# 2. Database (SQLite or PostgreSQL)
# 2. Database (SQLite, PostgreSQL)
# 3. Python Version
#
# Tests can run against either a single or multiple PostgreSQL databases.
Copy link
Member

Choose a reason for hiding this comment

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

technically Synapse can run against a sqlite and a postgres, though doing that seems slightly insane and the sytest setup scripts have no support for such a thing.

# This is configured by setting `MULTI_POSTGRES=1` in the environment.
#
# We mostly care about testing each topology.
# To vary the Python and Postgres versions, we use Docker images which are based
# on an assortment of Debian releases.
# - "py35" is Debian Stretch (Python 3.5, Postgres 9.6)
# - "py37" is Debian Buster (Python 3.7, Postgres 11)
# - "py38" is Debian Bullseye (Python 3.9, Postgres 13)
# - "py35" is Debian 9 Stretch (Python 3.5, Postgres 9.6)
# - "py37" is Debian 10 Buster (Python 3.7, Postgres 11)
# - "py38" is Debian 11 Bullseye (Python 3.9, Postgres 13)
#
# Our intent is to test:
# - Monolith:
# - Older Distro + SQLite
# - Older Python + Older PostgreSQL
# - Newer Python + Newer PostgreSQL
# - Workers:
# - Older Python + Older PostgreSQL
# - Newer Python + Newer PostgreSQL
# - Older Python + Older PostgreSQL (MULTI_POSTGRES)
# - Newer Python + Newer PostgreSQL (MULTI_POSTGRES)
# - Workers w/ Redis:
# - Newer Python + Newer PostgreSQL
#
Expand Down Expand Up @@ -335,7 +338,7 @@ steps:
style: "error"
retry: *retry_setup

- label: "SyTest Monolith :postgres: :debian 9:"
- label: "SyTest Monolith :postgres: :debian: 9"
agents:
queue: "medium"
env:
Expand Down