1
0

sytest-blacklist 1.7 KB

1234567891011121314151617181920212223242526272829303132333435363738
  1. # This file serves as a blacklist for SyTest tests that we expect will fail in
  2. # Synapse.
  3. #
  4. # Each line of this file is scanned by sytest during a run and if the line
  5. # exactly matches the name of a test, it will be marked as "expected fail",
  6. # meaning the test will still run, but failure will not mark the entire test
  7. # suite as failing.
  8. #
  9. # Test names are encouraged to have a bug accompanied with them, serving as an
  10. # explanation for why the test has been excluded.
  11. # Blacklisted due to https://github.com/matrix-org/synapse/issues/1679
  12. Remote room members also see posted message events
  13. # Blacklisted due to https://github.com/matrix-org/synapse/issues/2065
  14. Guest users can accept invites to private rooms over federation
  15. # Blacklisted due to https://github.com/vector-im/riot-web/issues/7211
  16. The only membership state included in a gapped incremental sync is for senders in the timeline
  17. # Blacklisted due to https://github.com/matrix-org/synapse/issues/1658
  18. Newly created users see their own presence in /initialSync (SYT-34)
  19. # Blacklisted due to https://github.com/matrix-org/synapse/issues/1396
  20. Should reject keys claiming to belong to a different user
  21. # Blacklisted due to https://github.com/matrix-org/synapse/issues/1531
  22. Enabling an unknown default rule fails with 404
  23. # Blacklisted due to https://github.com/matrix-org/synapse/issues/1663
  24. New federated private chats get full presence information (SYN-115)
  25. # Blacklisted due to https://github.com/matrix-org/matrix-doc/pull/2314 removing
  26. # this requirement from the spec
  27. Inbound federation of state requires event_id as a mandatory paramater
  28. # Blacklisted until https://github.com/matrix-org/synapse/pull/6486 lands
  29. Can upload self-signing keys