-
Notifications
You must be signed in to change notification settings - Fork 157
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
bug(e2e): Tenant Replications #1168
Comments
I witnessed this failure several times, despite the feature working as expected. This could be a nice issue for newcomers, happy to share more information on how to debug the failure and provide a fix, definitely something's race-ish. |
Hi @prometherion , I'd like to work on this issue. Could you please provide more details on how to reproduce the failure and any tips for debugging? Looking forward to contributing! |
Sorry for this late answer, @dev-saw99! Unfortunately, I've no idea why this is happening 😢 What I could suggest is trying back and for the incriminated test: after setting up the local environment, you can easily do this with the following command: Upon a failure, Capsule logs and current state must be investigated since I guess something raceish is happening 🤔 |
@prometherion Hey, I tried but I was not able to reproduce this issue. I will spend more time over this weekend and update here. Meanwhile, if you have any suggestions please let me know. |
Unfortunately, it seems it could be related to the whole test-suite. The single suggestion I could have here is to run it entirely, and wait for failures, and check Capsule logs. |
Bug description
The e2e tests for the tenant replications often fail:
They should be fixed, so we can rely on the status of our pipeline
The text was updated successfully, but these errors were encountered: