-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Android kokoro build is very flaky #6146
Comments
The Gradle build seems to hit memory limit easily after we adding |
Removing the highly flaky label as it is not seen again this week. It may also be possible that flakiness occurred after #6103 is by coincidence. |
#6103 actually seems a reasonable trigger, because it means the gradle task rebuilds more code. It looks like the failures resolved after #6131 was merged (it is the only PR between the last failure and first success), which is not wholly unreasonable. It isn't completely clear to me why that PR fixed it, but the change impacted gradle enough it does make some sense. I'm going to mark this as resolved. It could easily rear its head again, but it seems resolved for the while. |
Uh, oh. This may be resurfacing. I just saw https://source.cloud.google.com/results/invocations/8dcbb963-10c3-43e5-9345-9e0a3a7ed6b6 |
Actually. That's because it is on the v1.24.x branch. I guess we need a fix for the branch. |
An easy way to fix 1.24.x branch is to revert #6103 Edit: The "easy fix" above actually does not fix. |
@dapengzhang0, ah, yeah, that would probably work well. Would you mind sending out a PR? |
I encountered same issue of my backport to 24. this fix is also backported, so reopening the issue. |
@creamsoup This happens in some old branches (where #6131 is not in), even #6103 is reverted. |
okay. this is only happening in older branches, closing it. please reopen if this happens in |
Android kokoro build became very flaky after #6103
The text was updated successfully, but these errors were encountered: