-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[Disabled for Element-R] Flaky cypress test Read receipts > Paging up > After marking room as read, paging up to find old threads that were never read leaves the room read
#26341
[Disabled for Element-R] Flaky cypress test Read receipts > Paging up > After marking room as read, paging up to find old threads that were never read leaves the room read
#26341
Comments
in an attempt to fix flakes like: * element-hq/element-web#26298 * element-hq/element-web#26341 which appear to fail when using Rust crypto, possibly because the client takes a while to start up.
This looks like slow startup of the client. Hopefully fixed by matrix-org/matrix-react-sdk#11742 |
in an attempt to fix flakes like: * element-hq/element-web#26298 * element-hq/element-web#26341 which appear to fail when using Rust crypto, possibly because the client takes a while to start up.
https://github.com/matrix-org/matrix-js-sdk/actions/runs/6590996937/job/17908708726 Looking at the screenshots, there are two different failure modes here. The logs show it hanging at We don't seem to have useful logs, so I'm not really sure what happened here. In any case it seems likely to be yet another failure mode than the one observed |
https://github.com/matrix-org/matrix-js-sdk/actions/runs/6636711970/job/18029638156#step:8:913 It's very odd that this seems to affect the rust-crypto build so much more than the legacy crypto build. I could believe some sort of systemic "rust is slow" thing going on, but why only this test out of the entire set of read receipts tests? |
Read receipts > Paging up > After marking room as read, paging up to find old threads that were never read leaves the room read
Read receipts > Paging up > After marking room as read, paging up to find old threads that were never read leaves the room read
Read receipts > Paging up > After marking room as read, paging up to find old threads that were never read leaves the room read
Nope, didn't mean to close this. The |
I just ran this locally 10 times (with |
Leaving it for now though, because it uses Mark as Read, which we know has problems, that I am hoping to fix next. |
Flaky test Read receipts > Paging up "After marking room as read, paging up to find old threads that were never read leaves the room read"
The text was updated successfully, but these errors were encountered: