diff options
| author | Eric Eastwood <erice@element.io> | 2023-06-01 21:27:18 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-06-01 21:27:18 -0500 |
| commit | 30a5076da8ad776c150ad2745b5f34b4446012e0 (patch) | |
| tree | f2545745ea46c209767f94d157a4e9b6ee539e03 /scripts-dev/complement.sh | |
| parent | Merge branch 'release-v1.85' into develop (diff) | |
| download | synapse-30a5076da8ad776c150ad2745b5f34b4446012e0.tar.xz | |
Log when events are (unexpectedly) filtered out of responses in tests (#14213)
See https://github.com/matrix-org/synapse/pull/14095#discussion_r990335492 This is useful because when see that a relevant event is an `outlier` or `soft-failed`, then that's a good unexpected indicator explaining why it's not showing up. `filter_events_for_client` is used in `/sync`, `/messages`, `/context` which are all common end-to-end assertion touch points (also notifications, relations).
Diffstat (limited to 'scripts-dev/complement.sh')
| -rwxr-xr-x | scripts-dev/complement.sh | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/scripts-dev/complement.sh b/scripts-dev/complement.sh index cba2799f15..131f26234e 100755 --- a/scripts-dev/complement.sh +++ b/scripts-dev/complement.sh @@ -269,6 +269,10 @@ if [[ -n "$SYNAPSE_TEST_LOG_LEVEL" ]]; then export PASS_SYNAPSE_LOG_SENSITIVE=1 fi +# Log a few more useful things for a developer attempting to debug something +# particularly tricky. +export PASS_SYNAPSE_LOG_TESTING=1 + # Run the tests! echo "Images built; running complement" cd "$COMPLEMENT_DIR" |