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.

Sign up for GitHub

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

Jump to bottom

Fix occasional Jetifier build failures in Bazel #3759

Open
BenHenning opened this issue Sep 2, 2021 · 2 comments
Open

Fix occasional Jetifier build failures in Bazel #3759

BenHenning opened this issue Sep 2, 2021 · 2 comments
Labels
bug End user-perceivable behaviors which are not desirable. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Z-ibt Temporary label for Ben to keep track of issues he's triaged.

Comments

@BenHenning
Copy link
Member

When doing large Bazel builds locally (e.g. bazel build //app/...) I sometimes see flaky AndroidX/Jetifier failures that go away when building again. Given CI, this never seems to happen when building targets directly. It seems to be some sort of configuration flake or lack of hermeticity within the Android build pipeline configured by Bazel, but more investigation is needed.
@BenHenning BenHenning mentioned this issue Sep 2, 2021
Merged
6 tasks
@BenHenning BenHenning mentioned this issue Sep 14, 2021
Closed
@BenHenning BenHenning mentioned this issue Sep 26, 2021
Open
@deepanshu731 deepanshu731 mentioned this issue Sep 26, 2021
Merged
8 tasks
@BenHenning BenHenning mentioned this issue Sep 27, 2021
Closed
8 tasks
@BenHenning BenHenning mentioned this issue Oct 6, 2021
Merged
6 tasks
@BenHenning
Copy link
Member Author

We don't have a ton of data yet, but the last few develop runs seem really promising: https://github.com/oppia/oppia-android/commits/develop. Closing this as working.

@github-actions github-actions bot reopened this Oct 12, 2021
@github-actions
Copy link

The issue is reopened because of the following unresolved TODOs:

oppia-android/.github/workflows/unit_tests.yml

Line 236 in f266da8

# TODO(#3759): Remove this once there are no longer app test build failures.

oppia-android/.github/workflows/unit_tests.yml

Line 258 in f266da8

# TODO(#3759): Remove this once there are no longer app test build failures.

@BenHenning BenHenning added this to the Beta MR2 milestone Jun 11, 2022
@Broppia Broppia added issue_type_bug Impact: Low Low perceived user impact (e.g. edge cases). labels Jul 7, 2022
@BenHenning BenHenning added Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Z-ibt Temporary label for Ben to keep track of issues he's triaged. issue_user_developer and removed Impact: Low Low perceived user impact (e.g. edge cases). labels Sep 15, 2022
@BenHenning BenHenning removed this from the Beta MR2 milestone Sep 16, 2022
@seanlip seanlip added bug End user-perceivable behaviors which are not desirable. and removed issue_user_developer labels Mar 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug End user-perceivable behaviors which are not desirable. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Z-ibt Temporary label for Ben to keep track of issues he's triaged.
Projects
[Task Force] Migrate to Bazel - Android
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
3 participants
@seanlip @BenHenning @Broppia