diff options
| author | kegsay <kegan@matrix.org> | 2023-10-27 18:29:20 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-10-27 18:29:20 +0100 |
| commit | 11a8ae06325e9a8c9d57e3dff5fdf46a90309cd1 (patch) | |
| tree | 510f3d18a21c32e0dd114046b914eb0c9c0d5615 /flake.lock | |
| parent | Ensure local invited & knocking users leave before purge. (#16559) (diff) | |
| download | synapse-11a8ae06325e9a8c9d57e3dff5fdf46a90309cd1.tar.xz | |
complement: enable dirty runs (#16520)
* complement: enable dirty runs * Add changelog * Set a low connpool limit when running in Complement Dirty runs can cause many containers to be running concurrently, which seems to easily exhaust resources on the host. The increased speedup from dirty runs also seems to use more db connections on workers, which are misconfigured currently to have `SUM(workers * cp_max) > max_connections`, causing ``` FATAL: sorry, too many clients already ``` which results in tests failing. * Try p=2 concurrency to restrict slowness of servers which causes partial state join tests to flake * Debug logging * Only run flakey tests * Only adjust connection pool limits in worker mode * Move cp vars to somewhere where they get executed in CI * Move cp values back to where they actually work * Debug logging * Try p=1 to see if this makes worker mode happier * Remove debug logging
Diffstat (limited to 'flake.lock')
0 files changed, 0 insertions, 0 deletions