Skip to content

Sliding sync: omit bump stamp when it is unchanged #3455

Sliding sync: omit bump stamp when it is unchanged

Sliding sync: omit bump stamp when it is unchanged #3455

Triggered via pull request October 8, 2024 09:32
Status Failure
Total duration 38m 4s
Artifacts 4

tests.yml

on: pull_request
changes
2s
changes
check-lockfile
8s
check-lockfile
lint-crlf
7s
lint-crlf
lint-newsfile
38s
lint-newsfile
check-sampleconfig
56s
check-sampleconfig
check-schema-delta
47s
check-schema-delta
lint
5m 41s
lint
Typechecking
1m 43s
Typechecking
lint-pydantic
4m 41s
lint-pydantic
lint-clippy
0s
lint-clippy
lint-clippy-nightly
0s
lint-clippy-nightly
lint-rustfmt
0s
lint-rustfmt
lint-readme
0s
lint-readme
linting-done
4s
linting-done
Matrix: portdb
calculate-test-jobs
5s
calculate-test-jobs
Matrix: complement
Matrix: trial-pypy
Matrix: sytest
Matrix: trial
tests-done
3s
tests-done
Fit to window
Zoom out
Zoom in

Annotations

23 errors and 13 warnings
sytest (focal, multi-postgres, workers, asyncio)
Process completed with exit code 1.
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #308: /upgrade creates a new room
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #316: local user has push rules copied to upgraded room
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #317: remote user has push rules copied to upgraded room
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #528: Local device key changes appear in /keys/changes
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #532: Get left notifs for other users in sync and /keys/changes when user leaves
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #551: uploading self-signing key notifies over federation
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #552: uploading signed devices gets propagated over federation
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #584: Device messages over federation wake up /sync
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #588: Wildcard device messages over federation wake up /sync
sytest (focal, multi-postgres, workers, asyncio)
FAILURE: #679: Inbound federation rejects receipts from wrong remote
sytest (focal, multi-postgres, workers)
FAILURE: #167: Canonical alias can be set
sytest (focal, multi-postgres, workers)
FAILURE: #235: Guest users are kicked from guest_access rooms on revocation of guest_access over federation
sytest (focal, multi-postgres, workers)
FAILURE: #256: m.room.history_visibility == "invited" allows/forbids appropriately for Guest users
sytest (focal, multi-postgres, workers)
FAILURE: #257: m.room.history_visibility == "joined" allows/forbids appropriately for Guest users
sytest (focal, multi-postgres, workers)
FAILURE: #273: Guest users can sync from joined guest_access rooms if joined
sytest (focal, multi-postgres, workers)
FAILURE: #277: m.room.history_visibility == "invited" allows/forbids appropriately for Real users
sytest (focal, multi-postgres, workers)
FAILURE: #278: m.room.history_visibility == "joined" allows/forbids appropriately for Real users
sytest (focal, multi-postgres, workers)
FAILURE: #293: Real users can sync from invited guest_access rooms if joined
sytest (focal, multi-postgres, workers)
FAILURE: #296: Only see history_visibility changes on boundaries
sytest (focal, multi-postgres, workers)
FAILURE: #297: Backfill works correctly with history visibility set to joined
sytest (focal, multi-postgres, workers)
Process completed with exit code 1.
tests-done
Job sytest returned failure
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/
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/
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/
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/
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/
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, 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/
complement (monolith, SQLite)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
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/
complement (monolith, Postgres)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
complement (workers, Postgres)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

Artifacts

Produced during runtime
Name Size
Sytest Logs - failure - (focal, multi-postgres, workers) Expired
2.13 MB
Sytest Logs - failure - (focal, multi-postgres, workers, asyncio) Expired
2.08 MB
Sytest Logs - success - (focal) Expired
826 KB
Sytest Logs - success - (focal, postgres) Expired
844 KB