summary refs log tree commit diff
path: root/sytest-blacklist (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Back out implementation of MSC2314 (#12474)Richard van der Hoff2022-04-191-4/+0
| | | | | | | | MSC2314 has now been closed, so we're backing out its implementation, which originally happened in #6176. Unfortunately it's not a direct revert, as that PR mixed in a bunch of unrelated changes to tests etc.
* Blacklist new sytest validation test (#11270)Erik Johnston2021-11-081-0/+3
|
* Remove fixed and flakey tests from the sytest blacklist (#10788)David Robertson2021-09-101-10/+1
| | | We want to blacklist only known, consistent failures. We should deflake tests rather than ignoring them.
* Unblacklist fixed tests (#10357)Erik Johnston2021-07-091-4/+0
|
* Re-enable room v6 sytest (#10345)Richard van der Hoff2021-07-091-1/+0
| | | ... now that it has been fixed in https://github.com/matrix-org/sytest/pull/1061.
* Reenable 'Backfilled events whose prev_events...' sytest (#10292)Erik Johnston2021-07-011-1/+0
| | | Now that we've fixed it.
* Handle inbound events from federation asynchronously (#10272)Erik Johnston2021-06-291-0/+6
| | | | | | | | | | | 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.
* unblacklist some tests (#8474)Richard van der Hoff2020-10-071-3/+0
| | | | | 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.
* blacklist MSC2753 sytests until it's implemented in synapse (#8285)Matthew Hodgson2020-09-091-0/+8
| | | Dendrite's implementing MSC2753 over at https://github.com/matrix-org/dendrite/pull/1370 to prove the implementation for MSC purposes, and so sytest has sprouted tests for it over at https://github.com/matrix-org/sytest/pull/944. But we don't want them to run on synapse until synapse implements it.
* Back out perf regression from get_cross_signing_keys_from_cache. (#6494)Neil Johnson2019-12-091-0/+3
| | | Back out cross-signing code added in Synapse 1.5.0, which caused a performance regression.
* Implementation of MSC2314 (#6176)Amber Brown2019-11-281-1/+5
|
* Implement MSC2290 (#6043)Andrew Morgan2019-09-231-9/+0
| | | | | | | Implements MSC2290. This PR adds two new endpoints, /unstable/account/3pid/add and /unstable/account/3pid/bind. Depending on the progress of that MSC the unstable prefix may go away. This PR also removes the blacklist on some 3PID tests which occurs in #6042, as the corresponding Sytest PR changes them to use the new endpoints. Finally, it also modifies the account deactivation code such that it doesn't just try to deactivate 3PIDs that were bound to the user's account, but any 3PIDs that were bound through the homeserver on that user's account.
* Drop support for bind param on POST /account/3pid (MSC2290) (#6067)Andrew Morgan2019-09-201-0/+9
| | | As per [MSC2290](https://github.com/matrix-org/matrix-doc/pull/2290/files#diff-05cde9463e9209b701312b3baf2fb2ebR151), we're dropping the bind parameter from `/account/3pid`. This endpoint can now only be used for adding threepid's to the user's account on the homeserver.
* Unblacklist some user_directory sytests (#5637)Richard van der Hoff2019-07-091-4/+0
| | | Fixes https://github.com/matrix-org/synapse/issues/2306
* Add a sytest blacklist file (#5611)Andrew Morgan2019-07-051-0/+35
* Add a sytest blacklist file * Add changelog * Add blacklist to manifest
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-11-01 12:28:19 +0000