2019-07-04 09:24:13 -06:00
|
|
|
# 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)
|
2019-09-20 03:46:34 -06:00
|
|
|
|
|
|
|
|
# Blacklisted temporarily due to https://github.com/matrix-org/matrix-doc/pull/2290
|
|
|
|
|
# These sytests need to be updated with new endpoints, which will come in a later PR
|
|
|
|
|
# That PR will also remove this blacklist
|
|
|
|
|
Can bind 3PID via home server
|
|
|
|
|
Can bind and unbind 3PID via homeserver
|
|
|
|
|
3PIDs are unbound after account deactivation
|
|
|
|
|
Can bind and unbind 3PID via /unbind by specifying the identity server
|
|
|
|
|
Can bind and unbind 3PID via /unbind without specifying the identity server
|
