-
Notifications
You must be signed in to change notification settings - Fork 265
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
Integration tests for redaction failing #1069
Comments
This seems like an issue other people are facing too with hyper. Are we sharing the hyper client between multiple async runtimes perhaps? That's one way to trigger the error according to issues. These two seem to contain the most info: |
does |
Yes, that is what |
I think the main problem here is e2ee, so they are created for the entire test suite with the proper sled store in tmp (which he hold the tmpdir for so that it doesn't get scraped on drop), the other that we register with the server if they don't exist before (locally) - which saves a few roundtrips, too. I suppose we could change that. Maybe it does make sense to provide some TestClient that we can just hammer in some info (like the homeserver) to prevent the unnecessary roundtrips? |
The other option would be to not use |
since 1a57170 the redaction integration tests fail -
name_static
almost every time on CI, the other has been observed outside of CI to fail, too:The text was updated successfully, but these errors were encountered: