Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Complement TestDeviceListUpdates/when_joining_a_room_with_a_remote_user is flakey #580

Closed
DMRobertson opened this issue Sep 29, 2022 · 7 comments · Fixed by #593
Closed
Assignees
Labels

Comments

@DMRobertson
Copy link
Contributor

https://github.com/matrix-org/synapse/actions/runs/3149623842/jobs/5121449618#step:5:8174

Happened in worker mode---would guess there's some race the test isn't expecting?

@squahtx
Copy link
Contributor

squahtx commented Sep 29, 2022

related to matrix-org/synapse#13783

@squahtx
Copy link
Contributor

squahtx commented Sep 29, 2022

I reckon the tests are picking up the spurious device_lists.changed instead of the real one and advancing too early.

@squahtx squahtx changed the title Complement when_joining_a_room_with_a_remote_user is flakey(?) Complement TestDeviceListUpdates/when_joining_a_room_with_a_remote_user is flakey(?) Oct 3, 2022
@squahtx
Copy link
Contributor

squahtx commented Nov 14, 2022

@DMRobertson
Copy link
Contributor Author

@richvdh richvdh changed the title Complement TestDeviceListUpdates/when_joining_a_room_with_a_remote_user is flakey(?) Complement TestDeviceListUpdates/when_joining_a_room_with_a_remote_user is flakey Jan 10, 2023
@richvdh richvdh transferred this issue from matrix-org/synapse Jan 10, 2023
@DMRobertson
Copy link
Contributor Author

squahtx pushed a commit that referenced this issue Feb 1, 2023
When a remote user has a device list update, an entry is expected to appear in
`device_lists.changed` in the `/sync` response. The local homeserver may then
query the remote homeserver for the update. Some homeservers (Synapse) may emit
extra `device_lists.changed` updates in `/sync` responses after querying keys.

Previously, we attempted to skip over the spurious `device_lists.changed`
updates by doing another sync. This wasn't sufficient, so we make another
remote user send a device list update, and wait for that to appear.

Fixes #580.

Signed-off-by: Sean Quah <[email protected]>
squahtx added a commit that referenced this issue Feb 1, 2023
When a remote user has a device list update, an entry is expected to appear in
`device_lists.changed` in the `/sync` response. The local homeserver may then
query the remote homeserver for the update. Some homeservers (Synapse) may emit
extra `device_lists.changed` updates in `/sync` responses after querying keys.

Previously, we attempted to skip over the spurious `device_lists.changed`
updates by doing another sync. This wasn't sufficient, so we make another
remote user send a device list update, and wait for that to appear.

Fixes #580.

Signed-off-by: Sean Quah <[email protected]>
@squahtx squahtx self-assigned this Feb 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants