-
Notifications
You must be signed in to change notification settings - Fork 541
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
Partially fix #2844: force Gradle tests to run on JDK 9 in CI #2845
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Remove kapt workaround since per google/dagger#1449 (comment) this should be fixed in the version of Kotlin that we're now using.
Add check for Java versions for Gradle CI workflows.
Add more diagnostics for verifying Java environment, and try further to force Gradle to use the one that's installed.
Add explicit javax annotations dependency per google/dagger#1449 (comment).
Add explicit javax annotations dependency per google/dagger#1449 (comment).
Add explicit javax annotations dependency per google/dagger#1449 (comment).
Add explicit javax annotations dependency per google/dagger#1449 (comment).
Add explicit javax annotations dependency per google/dagger#1449 (comment).
BenHenning
commented
Mar 6, 2021
BenHenning
commented
Mar 6, 2021
BenHenning
commented
Mar 6, 2021
BenHenning
commented
Mar 6, 2021
BenHenning
commented
Mar 6, 2021
Add additional dependencies due to Java EE libraries being deprecated/removed JDK 9+ per: https://stackoverflow.com/a/43574427.
vinitamurthi
approved these changes
Mar 8, 2021
anandwana001
approved these changes
Mar 8, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks! |
techjd
pushed a commit
to techjd/oppia-android
that referenced
this pull request
Mar 9, 2021
…ppia#2845) * Update build.gradle Remove kapt workaround since per google/dagger#1449 (comment) this should be fixed in the version of Kotlin that we're now using. * Update main.yml Add check for Java versions for Gradle CI workflows. * Update main.yml Add more diagnostics for verifying Java environment, and try further to force Gradle to use the one that's installed. * Update app/build.gradle Add explicit javax annotations dependency per google/dagger#1449 (comment). * Update data/build.gradle Add explicit javax annotations dependency per google/dagger#1449 (comment). * Update domain/build.gradle Add explicit javax annotations dependency per google/dagger#1449 (comment). * Update testing/build.gradle Add explicit javax annotations dependency per google/dagger#1449 (comment). * Update utility/build.gradle Add explicit javax annotations dependency per google/dagger#1449 (comment). * Apply suggestions from code review Add additional dependencies due to Java EE libraries being deprecated/removed JDK 9+ per: https://stackoverflow.com/a/43574427.
techjd
added a commit
to techjd/oppia-android
that referenced
this pull request
Mar 9, 2021
…in CI (oppia#2845)" This reverts commit 15e928f.
techjd
added a commit
to techjd/oppia-android
that referenced
this pull request
Mar 9, 2021
…in CI (oppia#2845)" This reverts commit 15e928f.
techjd
pushed a commit
to techjd/oppia-android
that referenced
this pull request
Mar 9, 2021
…ppia#2845) * Update build.gradle Remove kapt workaround since per google/dagger#1449 (comment) this should be fixed in the version of Kotlin that we're now using. * Update main.yml Add check for Java versions for Gradle CI workflows. * Update main.yml Add more diagnostics for verifying Java environment, and try further to force Gradle to use the one that's installed. * Update app/build.gradle Add explicit javax annotations dependency per google/dagger#1449 (comment). * Update data/build.gradle Add explicit javax annotations dependency per google/dagger#1449 (comment). * Update domain/build.gradle Add explicit javax annotations dependency per google/dagger#1449 (comment). * Update testing/build.gradle Add explicit javax annotations dependency per google/dagger#1449 (comment). * Update utility/build.gradle Add explicit javax annotations dependency per google/dagger#1449 (comment). * Apply suggestions from code review Add additional dependencies due to Java EE libraries being deprecated/removed JDK 9+ per: https://stackoverflow.com/a/43574427.
Just hit this issue again in #2871. :( |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes part of #2844.
This aims to fix the OpenJDK flakes happening for Gradle tests (per #2844) by forcing the CI environment to use JDK 9 instead of JDK 8 for runtime, since it seems that JDK 8 may have an issue where the JVM can crash when managing many forks (we updated Gradle tests to use forks a while back). However, making the CI environment properly use JDK 9 for Gradle involved a few steps:
Some things to note:
We will not actually be able to verify if the issue is fixed until we see no new instances of the crash crop up over the next few weeks. Given that the issue seems to only reproduce occasionally when running the whole batch of tests, it's difficult to make the issue commonplace enough to gain certainty it's been fixed. Given the low volume of the flake, though, waiting a few weeks to ensure it's gone should be reasonable.