-
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
[Due for payment 2025-02-26] [$50] Flaky tests/ui/GroupChatNameTests.tsx test #56057
Comments
Triggered auto assignment to @sakluger ( |
Job added to Upwork: https://www.upwork.com/jobs/~021884927641362998630 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @fedirjh ( |
Upwork job price has been updated to $50 |
@rezkiy37 can you check, this first time happened after your PR https://github.com/Expensify/App/pull/54958/files |
@mountiny, the issue has been solved by re-runing - #56051 (comment). ![]() |
Hi, I am Michael (Mykhailo) from Callstack, an expert agency and I can work on this issue. |
I am testing it locally. Currently, it always works properly on the latest main for me. |
I can't reproduce on local First time the error occurred in logs https://github.com/Expensify/App/actions/runs/13039925713 Maybe it was the package update that changed it? suggest trying to reproduce with old package version |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@mountiny So, it is reproducible Could you share more details about the env settings for the CI? (especially that specific for this flow) |
@mountiny bump here |
We just talked about it. We faced a few strange moments:
cc @mountiny |
Just a friendly reminder here #56057 (comment). |
We've found one more possible root cause of the problem. We compared commands that we launch locally and CI does remotely.
As you can see they are slightly different. CI uses a couple of parameters for jest. We've tried to add them locally and it works well. However, we faced a crucial discrepancy - |
I will update the PR with a CI patch to npm to test it remotely Do we have any specific reasons for using npx? |
I've updated the workflow - not failed now |
I’m planning a short vacation next week from Monday to Wednesday, from the 17th to the 19th. I am working on the issue later. |
Sorry had been ooo last week |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.0-2 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 2025-02-26. 🎊 For reference, here are some details about the assignees on this issue:
|
@fedirjh @sakluger @fedirjh The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
No payments or regression tests required |
Problem
The tests/ui/GroupChatNameTests.tsx test https://github.com/Expensify/App/actions/runs/13051191486/job/36411651957 is now failing in main and its not clear what is causing it, lets investigate and fix it.
EDIT: This is also affecting the test below ("Should show last message preview in LHN"): https://github.com/Expensify/App/actions/runs/13051191486/job/36411651957
This test seems to be flaky as it is passign after restart here https://github.com/Expensify/App/actions/runs/13050631537
Solution
Identify the offending PR that made if flaky - the test has been around for 6 months so something had to make it flaky recently
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @saklugerThe text was updated successfully, but these errors were encountered: