-
Notifications
You must be signed in to change notification settings - Fork 626
Rollback #2785, which made bom generation and crashlytics smoke test fail. #2825
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
Conversation
Coverage ReportAffected SDKs
Test Logs
NotesHTML coverage reports can be produced locally with Head commit (e6d4114c) is created by Prow via merging commits: 0d95ad5 9ea5cc0. |
Binary Size ReportAffected SDKsNo changes between base commit (0d95ad5) and head commit (e6d4114c). Test Logs
NotesHead commit (e6d4114c) is created by Prow via merging commits: 0d95ad5 9ea5cc0. |
This reverts commit 20cd7fa.
@yifanyang: The following test failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
The problems are:
Despite of the crashlytics errors, to fix the bom task, I will need to build and push a new CI image. It's probably easier to rollback at this moment. Can you help me approve this PR? The current approach of decoupling sdk and smoke test gradle requires below changes to be pushed (or reverted) at the same time:
And not sure if I'm still missing some use case. I'll try to think of a cleaner way to do this. |
No description provided.