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

Flaky cypress test: Cryptography > event shields > should show the correct shield on e2e events #26274

Closed
richvdh opened this issue Oct 2, 2023 · 4 comments
Labels

Comments

@richvdh
Copy link
Member

richvdh commented Oct 2, 2023

   1) Cryptography
       event shields
         should show the correct shield on e2e events:
     AssertionError: Timed out retrying after 10000ms: expected '<li.mx_EventTile.mx_EventTile_continuation.mx_EventTile_last.mx_EventTile_lastInSection.mx_EventTile_bad>' to contain 'test encrypted 1'
      at Context.eval (webpack:///./cypress/e2e/crypto/crypto.spec.ts:318:0)

https://github.com/matrix-org/matrix-react-sdk/actions/runs/6379116260/job/17310975290#step:8:21497

@richvdh richvdh added Z-Flaky-Test A test is raising false alarms T-Defect A-Developer-Experience labels Oct 2, 2023
@richvdh
Copy link
Member Author

richvdh commented Oct 2, 2023

hrm, this actually happened twice on the same PR (matrix-org/matrix-react-sdk#11687), so it might somehow be a problem with that PR rather than a real flaky test.

@richvdh
Copy link
Member Author

richvdh commented Oct 2, 2023

Ah, I think the problem is that that test has always been a bit flaky, but up until now it has been masked by the automatic retries. That PR adds even more flakiness so it is no longer masked.

@richvdh
Copy link
Member Author

richvdh commented Oct 2, 2023

The problem here seems to be that, even though the to-device message carrying the message key arrived, it wasn't decrypted. It's unclear to me why this might have happened, though it rather looks as though things froze for a while.

@richvdh
Copy link
Member Author

richvdh commented Jan 19, 2024

since this hasn't been reported for several months, let's assume for now that it is fixed.

@richvdh richvdh closed this as completed Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant