Skip to content
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

Investigate workflow job failing on main: e2ePerformanceTests / Build apk from delta ref #47668

Open
github-actions bot opened this issue Aug 19, 2024 · 7 comments
Assignees
Labels

Comments

@github-actions
Copy link
Contributor

🚨 Failure Summary 🚨:

⚠️ Action Required ⚠️:

🛠️ A recent merge appears to have caused a failure in the job named e2ePerformanceTests / Build apk from delta ref.
This issue has been automatically created and labeled with Workflow Failure for investigation.

👀 Please look into the following:

  1. Why the PR caused the job to fail?
  2. Address any underlying issues.

🐛 We appreciate your help in squashing this bug!

@stitesExpensify
Copy link
Contributor

@bernhardoj do you know what is causing this?

@bernhardoj
Copy link
Contributor

I was trying to run the test locally, but looks like there are some env variables that are not available on the repo.
image

The error log is also blank
image

I currently have no idea.

@kirillzyusko
Copy link
Contributor

image

We need to increase java heap size for build process to make builds more stable 👀

Feel free to assign me on this issue and I can help with that 🙌

@stitesExpensify
Copy link
Contributor

Assigned. Thank you very much @kirillzyusko !

@kirillzyusko
Copy link
Contributor

Opened a PR here: #47847

It's ready for review 😊

@kirillzyusko
Copy link
Contributor

I think the issue can be closed because the PR was merged

@melvin-bot melvin-bot bot added Monthly KSv2 and removed Weekly KSv2 labels Oct 2, 2024
Copy link

melvin-bot bot commented Oct 2, 2024

This issue has not been updated in over 15 days. @kirillzyusko, @stitesExpensify eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants