Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Linearizer uses a different reactor than the homeserver during tests #12841

Open
squahtx opened this issue May 23, 2022 · 0 comments
Open

Linearizer uses a different reactor than the homeserver during tests #12841

squahtx opened this issue May 23, 2022 · 0 comments
Labels
A-Testing Issues related to testing in complement, synapse, etc T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues.

Comments

@squahtx
Copy link
Contributor

squahtx commented May 23, 2022

When there is contention, Linearizer sleeps upon acquiring a lock and thus needs access to a reactor.
It turns out that the reactor used by Linearizer is different to the reactor used by the HomeServer during tests.
There is no Linearizer contention in our tests, so we don't notice this bug.
@squahtx squahtx added the T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues. label May 23, 2022
@richvdh richvdh added A-Testing Issues related to testing in complement, synapse, etc and removed z-testing labels Aug 25, 2022
@matrixbot matrixbot mentioned this issue Dec 21, 2023
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
A-Testing Issues related to testing in complement, synapse, etc T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@MadLittleMods @richvdh @squahtx