Skip to content
Tests

Fix MSC4222 returning full state #3841

Sign in to view logs

Fix MSC4222 returning full state

Fix MSC4222 returning full state #3841

Triggered via pull request November 8, 2024 14:25
@erikjohnstonerikjohnston
synchronize #17915
erikj/fix_msc4222
Status Cancelled
Total duration 11m 13s
Artifacts 4

tests.yml

on: pull_request
changes
2s
changes
check-lockfile
8s
check-lockfile
lint-crlf
4s
lint-crlf
lint-newsfile
33s
lint-newsfile
check-sampleconfig
45s
check-sampleconfig
check-schema-delta
40s
check-schema-delta
lint
32s
lint
Typechecking
1m 29s
Typechecking
lint-pydantic
50s
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
2s
linting-done
Matrix: portdb
calculate-test-jobs
8s
calculate-test-jobs
Matrix: complement
trial-olddeps
7m 21s
trial-olddeps
cargo-test
0s
cargo-test
cargo-bench
0s
cargo-bench
Matrix: trial-pypy
export-data
2m 12s
export-data
Matrix: sytest
Matrix: trial
tests-done
3s
tests-done
Fit to window
Zoom out
Zoom in

Annotations

52 errors and 12 warnings
sytest (bullseye)
Canceling since a higher priority waiting request for 'Tests-refs/pull/17915/merge' exists
sytest (bullseye)
The operation was canceled.
sytest (bullseye)
FAILURE: #314: /upgrade copies important state to the new room
sytest (bullseye)
FAILURE: #338: Full state sync includes joined rooms
sytest (bullseye)
FAILURE: #356: State from remote users is included in the state in the initial sync
sytest (bullseye)
FAILURE: #358: Changes to state are included in an gapped incremental sync
sytest (bullseye)
FAILURE: #360: A full_state incremental update returns all state
sytest (bullseye)
FAILURE: #361: When user joins a room the state is included in the next sync
sytest (bullseye)
FAILURE: #362: A change to displayname should not result in a full state sync
sytest (bullseye)
FAILURE: #364: When user joins a room the state is included in a gapped sync
sytest (bullseye)
FAILURE: #365: When user joins and leaves a room in the same batch, the full state is still included in the next sync
sytest (bullseye)
FAILURE: #374: Left rooms appear in the leave section of sync
sytest (bullseye, multi-postgres, workers, asyncio)
Canceling since a higher priority waiting request for 'Tests-refs/pull/17915/merge' exists
sytest (bullseye, multi-postgres, workers, asyncio)
The operation was canceled.
sytest (bullseye, multi-postgres, workers, asyncio)
FAILURE: #314: /upgrade copies important state to the new room
sytest (bullseye, multi-postgres, workers, asyncio)
FAILURE: #338: Full state sync includes joined rooms
sytest (bullseye, multi-postgres, workers, asyncio)
FAILURE: #356: State from remote users is included in the state in the initial sync
sytest (bullseye, multi-postgres, workers, asyncio)
FAILURE: #358: Changes to state are included in an gapped incremental sync
sytest (bullseye, multi-postgres, workers, asyncio)
Process completed with exit code 1.
sytest (bullseye, multi-postgres, workers)
Canceling since a higher priority waiting request for 'Tests-refs/pull/17915/merge' exists
sytest (bullseye, multi-postgres, workers)
The operation was canceled.
sytest (bullseye, multi-postgres, workers)
FAILURE: #314: /upgrade copies important state to the new room
sytest (bullseye, multi-postgres, workers)
FAILURE: #338: Full state sync includes joined rooms
sytest (bullseye, multi-postgres, workers)
FAILURE: #356: State from remote users is included in the state in the initial sync
sytest (bullseye, multi-postgres, workers)
FAILURE: #358: Changes to state are included in an gapped incremental sync
sytest (bullseye, multi-postgres, workers)
FAILURE: #360: A full_state incremental update returns all state
sytest (bullseye, multi-postgres, workers)
FAILURE: #361: When user joins a room the state is included in the next sync
sytest (bullseye, multi-postgres, workers)
FAILURE: #362: A change to displayname should not result in a full state sync
sytest (bullseye, multi-postgres, workers)
FAILURE: #364: When user joins a room the state is included in a gapped sync
sytest (bullseye, multi-postgres, workers)
FAILURE: #365: When user joins and leaves a room in the same batch, the full state is still included in the next sync
sytest (bullseye, multi-postgres, workers)
FAILURE: #374: Left rooms appear in the leave section of sync
sytest (bullseye, postgres)
Canceling since a higher priority waiting request for 'Tests-refs/pull/17915/merge' exists
sytest (bullseye, postgres)
The operation was canceled.
sytest (bullseye, postgres)
FAILURE: #314: /upgrade copies important state to the new room
sytest (bullseye, postgres)
FAILURE: #338: Full state sync includes joined rooms
sytest (bullseye, postgres)
FAILURE: #356: State from remote users is included in the state in the initial sync
sytest (bullseye, postgres)
FAILURE: #358: Changes to state are included in an gapped incremental sync
sytest (bullseye, postgres)
FAILURE: #360: A full_state incremental update returns all state
sytest (bullseye, postgres)
FAILURE: #361: When user joins a room the state is included in the next sync
sytest (bullseye, postgres)
FAILURE: #362: A change to displayname should not result in a full state sync
sytest (bullseye, postgres)
FAILURE: #364: When user joins a room the state is included in a gapped sync
sytest (bullseye, postgres)
FAILURE: #365: When user joins and leaves a room in the same batch, the full state is still included in the next sync
sytest (bullseye, postgres)
FAILURE: #374: Left rooms appear in the leave section of sync
complement (workers, Postgres)
Canceling since a higher priority waiting request for 'Tests-refs/pull/17915/merge' exists
complement (workers, Postgres)
The operation was canceled.
complement (monolith, Postgres)
Canceling since a higher priority waiting request for 'Tests-refs/pull/17915/merge' exists
complement (monolith, Postgres)
The operation was canceled.
complement (monolith, SQLite)
Canceling since a higher priority waiting request for 'Tests-refs/pull/17915/merge' exists
complement (monolith, SQLite)
The operation was canceled.
trial (3.9, postgres, 11, all)
Canceling since a higher priority waiting request for 'Tests-refs/pull/17915/merge' exists
trial (3.9, postgres, 11, all)
The operation was canceled.
tests-done
Job trial returned cancelled
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/
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/
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/
portdb (3.13, 17)
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.9, 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.9, 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/
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.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/
complement (workers, Postgres)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
complement (monolith, Postgres)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
complement (monolith, SQLite)
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 - cancelled - (bullseye)
31.4 KB
Sytest Logs - cancelled - (bullseye, multi-postgres, workers)
23.3 KB
Sytest Logs - cancelled - (bullseye, multi-postgres, workers, asyncio)
8.52 KB
Sytest Logs - cancelled - (bullseye, postgres)
23.9 KB