Sliding sync: Add connection tracking to the account_data
extension…
#10
tests.yml
on: push
changes
1s
check-sampleconfig
5m 39s
check-schema-delta
18s
lint
5m 41s
Typechecking
4m 27s
lint-pydantic
5m 40s
lint-clippy
1m 6s
lint-clippy-nightly
1m 11s
lint-rustfmt
47s
lint-readme
10s
Matrix: portdb
Matrix: complement
Matrix: trial-pypy
tests-done
2s
Annotations
26 errors and 15 warnings
sytest (testing, postgres)
FAILURE: #594: After /purge_history users still get pushed for new messages
|
sytest (testing, postgres)
Process completed with exit code 1.
|
sytest (testing, postgres)
Process completed with exit code 1.
|
sytest (focal, multi-postgres, workers)
FAILURE: #181: Invited user can reject invite over federation
|
sytest (focal, multi-postgres, workers)
FAILURE: #182: Invited user can reject invite over federation several times
|
sytest (focal, multi-postgres, workers)
FAILURE: #184: Invited user can reject invite over federation for empty room
|
sytest (focal, multi-postgres, workers)
FAILURE: #187: Remote invited user can see room metadata
|
sytest (focal, multi-postgres, workers)
FAILURE: #220: Can invite unbound 3pid over federation
|
sytest (focal, multi-postgres, workers)
FAILURE: #222: Can invite unbound 3pid over federation with no ops into a private room
|
sytest (focal, multi-postgres, workers)
FAILURE: #223: Can invite unbound 3pid over federation with users from both servers
|
sytest (focal, multi-postgres, workers)
FAILURE: #317: remote user has push rules copied to upgraded room
|
sytest (focal, multi-postgres, workers)
FAILURE: #319: /upgrade moves remote aliases to the new room
|
sytest (focal, multi-postgres, workers)
FAILURE: #328: Local and remote users' homeservers remove a room from their public directory on upgrade
|
sytest (focal, multi-postgres, workers)
Process completed with exit code 1.
|
sytest (focal, multi-postgres, workers, asyncio)
Process completed with exit code 1.
|
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #148: Remote users can join room by alias
|
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #154: New room members see first user's profile information in per-room initialSync
|
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #163: Message history can be paginated over federation
|
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #182: Invited user can reject invite over federation several times
|
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #192: Remote banned user is kicked and may not rejoin until unbanned
|
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #235: Guest users are kicked from guest_access rooms on revocation of guest_access over federation
|
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #241: Guest users denied access over federation if guest access prohibited
|
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #246: Typing notification sent to local room members
|
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #248: Typing can be explicitly stopped
|
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #319: /upgrade moves remote aliases to the new room
|
tests-done
Job sytest returned failure
|
Typechecking
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
check-sampleconfig
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
lint-pydantic
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
trial (3.12, sqlite, all)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
portdb (3.11, 15)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
portdb (3.8, 11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
trial (3.11, sqlite, all)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
trial (3.8, sqlite)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
trial (3.8, sqlite, all)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
trial (3.10, sqlite, all)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
trial (3.9, sqlite, all)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
trial (3.12, postgres, 16, all)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
export-data
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
trial (3.8, postgres, 11, all)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
Sytest Logs - failure - (focal, multi-postgres, workers)
|
1.79 MB |
|
Sytest Logs - failure - (focal, multi-postgres, workers, asyncio)
|
2.04 MB |
|
Sytest Logs - failure - (testing, postgres)
|
846 KB |
|
Sytest Logs - success - (focal)
|
825 KB |
|
Sytest Logs - success - (focal, asyncio)
|
838 KB |
|
Sytest Logs - success - (focal, postgres)
|
842 KB |
|
Sytest Logs - success - (focal, postgres, asyncio)
|
847 KB |
|