mirror of
https://mau.dev/maunium/synapse.git
synced 2024-12-14 18:43:53 +01:00
c54db67d0e
Fixes #9490 This will break a couple of SyTest that are expecting failures to be added to the response of a federation /send, which obviously doesn't happen now that things are asynchronous. Two drawbacks: Currently there is no logic to handle any events left in the staging area after restart, and so they'll only be handled on the next incoming event in that room. That can be fixed separately. We now only process one event per room at a time. This can be fixed up further down the line.
49 lines
2.2 KiB
Text
49 lines
2.2 KiB
Text
# This file serves as a blacklist for SyTest tests that we expect will fail in
|
|
# Synapse.
|
|
#
|
|
# Each line of this file is scanned by sytest during a run and if the line
|
|
# exactly matches the name of a test, it will be marked as "expected fail",
|
|
# meaning the test will still run, but failure will not mark the entire test
|
|
# suite as failing.
|
|
#
|
|
# Test names are encouraged to have a bug accompanied with them, serving as an
|
|
# explanation for why the test has been excluded.
|
|
|
|
# Blacklisted due to https://github.com/matrix-org/synapse/issues/1679
|
|
Remote room members also see posted message events
|
|
|
|
# Blacklisted due to https://github.com/matrix-org/synapse/issues/2065
|
|
Guest users can accept invites to private rooms over federation
|
|
|
|
# Blacklisted due to https://github.com/vector-im/riot-web/issues/7211
|
|
The only membership state included in a gapped incremental sync is for senders in the timeline
|
|
|
|
# Blacklisted due to https://github.com/matrix-org/synapse/issues/1658
|
|
Newly created users see their own presence in /initialSync (SYT-34)
|
|
|
|
# Blacklisted due to https://github.com/matrix-org/synapse/issues/1396
|
|
Should reject keys claiming to belong to a different user
|
|
|
|
# Blacklisted due to https://github.com/matrix-org/synapse/issues/1531
|
|
Enabling an unknown default rule fails with 404
|
|
|
|
# Blacklisted due to https://github.com/matrix-org/synapse/issues/1663
|
|
New federated private chats get full presence information (SYN-115)
|
|
|
|
# Blacklisted due to https://github.com/matrix-org/matrix-doc/pull/2314 removing
|
|
# this requirement from the spec
|
|
Inbound federation of state requires event_id as a mandatory paramater
|
|
|
|
# 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
|
|
We can't peek into rooms with invited history_visibility
|
|
We can't peek into rooms with joined history_visibility
|
|
Local users can peek by room alias
|
|
Peeked rooms only turn up in the sync for the device who peeked them
|
|
|
|
|
|
# Blacklisted due to changes made in #10272
|
|
Outbound federation will ignore a missing event with bad JSON for room version 6
|
|
Backfilled events whose prev_events are in a different room do not allow cross-room back-pagination
|
|
Federation rejects inbound events where the prev_events cannot be found
|