-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[HOLD for payment 2024-12-25] E2E: Improve stability of linking test #52813
Comments
I am available to look into this issue so feel free to assign me (Hanno from margelo here who built the e2e pipeline) 😊 |
Triggered auto assignment to @puneetlath, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.76-12 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-12-25. 🎊 For reference, here are some details about the assignees on this issue:
|
Is this still ongoing? |
The pipeline is currently working. I'm now fixing issues here and adding new e2e tests. Do you have anything specific you'd like me to look into? |
Nothing in particular. Just wondering about the status of this issue and whether it still needs to be open. |
We received one reaction so far, but to be honest, it looks like a valid one. |
Issue is ready for payment but no BZ is assigned. @anmurali you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks! |
Payment Summary
BugZero Checklist (@anmurali)
|
@puneetlath, @eVoloshchak, @anmurali, @hannojg Huh... This is 4 days overdue. Who can take care of this? |
Ok sounds good @perunt. I think all that's left then is for @anmurali to pay out @eVoloshchak. |
Payment Summary
|
$250 approved for @eVoloshchak |
The e2e test pipeline produces a false positive now once a day on average. It is always the linking test that turns out false positive.
We should investigate why that test is unstable and fix it (it could also mean that there is actually a performance problem on that screen that causes performance to fluctuate).
Examples of false positives are:
Issue Owner
Current Issue Owner: @anmuraliThe text was updated successfully, but these errors were encountered: