-
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 2023-09-29] Tests in the App repo are not passing when we use onyx version with Batched updates #27470
Comments
Triggered auto assignment to @JmillsExpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to @marcaaron, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Gonna take the Bug label off, but happy to help review this PR. |
I believe we are waiting for a few regressions to be addressed. Margelo is traveling atm so probably this might take a couple days to close out. @tgolen has an approving review on the PR. I'm going to give the code another look now. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.72-11 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 2023-09-29. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
@Szymon20000, @marcaaron Whoops! This issue is 2 days overdue. Let's get this updated quick! |
We merged this PR and it's on production so I think there is nothing left to do here besides pay out the C+ who got tagged in for a review / testing. Gonna add BZ to help with this part now. |
Triggered auto assignment to @tjferriss ( |
Bug0 Triage Checklist (Main S/O)
|
@tjferriss This one is on production already - we just need help paying out @allroundexperts for the help in testing / reviewing. |
@allroundexperts I've sent you an offer via Upworks for payment: https://www.upwork.com/jobs/~01b16f58f5af83ea0b |
@tjferriss I get paid through the App. Can you please write a payment summary and I'll request the amount! |
Payment summary: Contributor+ Review: @allroundexperts $500 |
Requested. Thanks @tjferriss! |
$500 payment approved for @allroundexperts based on BZ summary. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Apply onyx batching feature and run
rpm run test
Expected Result:
All tests should be passing
Actual Result:
Some of them are failing
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number:
Reproducible in staging?:
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: