summary refs log tree commit diff
path: root/sytest-blacklist
diff options
context:
space:
mode:
authorRichard van der Hoff <1389908+richvdh@users.noreply.github.com>2020-10-07 13:39:50 +0100
committerGitHub <noreply@github.com>2020-10-07 13:39:50 +0100
commitd373ec2f72f69ae6c394482df89061302be41405 (patch)
tree79c309929eb5577601d9cc3426291520c93769ea /sytest-blacklist
parentAdd support for MSC2697: Dehydrated devices (#8380) (diff)
downloadsynapse-d373ec2f72f69ae6c394482df89061302be41405.tar.xz
unblacklist some tests (#8474)
It seems most of these blacklisted tests do actually pass most of the time.

I'm of the opinion that having them blacklisted here means there is very little incentive for us to deflake any flaky tests, and meanwhile any value in those tests is completely lost.
Diffstat (limited to '')
-rw-r--r--sytest-blacklist3
1 files changed, 0 insertions, 3 deletions
diff --git a/sytest-blacklist b/sytest-blacklist
index b563448016..de9986357b 100644
--- a/sytest-blacklist
+++ b/sytest-blacklist
@@ -34,9 +34,6 @@ New federated private chats get full presence information (SYN-115)
 # this requirement from the spec
 Inbound federation of state requires event_id as a mandatory paramater
 
-# Blacklisted until https://github.com/matrix-org/synapse/pull/6486 lands
-Can upload self-signing keys
-
 # Blacklisted until MSC2753 is implemented
 Local users can peek into world_readable rooms by room ID
 We can't peek into rooms with shared history_visibility