-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Add missing worker types to Complement worker-mode runs #14871
Conversation
We were missing some possible worker types from the list that is used in CI and complement.sh. This will likely cause CI to be slower, but comes with the benefit of more complete test coverage. 'account_data' being missing from this list caused CI to not catch #14869.
Looks like this is bringing up May need to bump the Postgres database connection limit to avoid false negatives. Adding synapse/docker/complement/Dockerfile Lines 28 to 30 in a7b54ca
I put mine right under here so it is inherited into the synapse database that gets created. A bunch of these
Followed by: One of these
Default on Postgres is 100 connections.
Then there is the reserved connections Postgres likes to keep to(3 I think?). |
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.
Looks like this is good to go. Any reason for keeping this in draft?
I think the CI failure aren't taken care of still: #14871 (comment) |
Oh, I see. I thought that referred to "just" a flake, but I guess it's atest failure that's been exposed by this change(?) |
Yeah, I don't think it is a flake, but a failure! |
…plement_worker_add_types
CI is passing, now that #14869 has merged. However it looks like the time it takes to run Complement worker tests nearly doubles with this change. The time it typically takes for the Complement Synapse container to be deployed when starting a new Complement test run is ~12s: https://github.com/matrix-org/synapse/actions/runs/4322697303/jobs/7545484048#step:6:7831 After this change, we're seeing more like ~22-23s: https://github.com/matrix-org/synapse/actions/runs/4322703753/jobs/7545484103#step:6:7990 This is significant, as this bump is applied to every test. So while typical runtimes for a Complement workers test run is ~36m. With this change, the run time becomes ~1h. Still, I think this is worth it for correctness - though it would be nice to pair it with some performance work to maintain (relatively) low running times for Complement worker runs in CI. |
Elegantly superseded by #14921 🎉 |
We were missing some possible worker types from the list that is used in CI and complement.sh.
This will likely cause CI to be slower, but comes with the benefit of more complete integration test coverage.Surprisingly, it looks to have not made it much slower. The action in this PR took 38m 13s, whereas the equivalent action in #14869 took 37m 18s.That was tested when workers were failing to start up. The actual deploy times look to have gone up significantly with this change.'account_data' being missing from this list caused CI to not catch #14869.
As such, CI is expected to fail until that PR is merged.merged.