Run setup-java for Firestore emulator in GitHub Actions #975
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.
Fix a problem where the Firestore integration tests were flakily failing in GitHub Actions runners due to the Firestore emulator failing to start.
If the GitHub Actions runner selected for integration testing had JDK 8 installed then the Firestore emulator would fail to start because recent releases of the Firestore emulator require JDK 11 or newer. This would cause the tests that attempt to communicate with the Firestore emulator to understandably fail.
The fix is to explicitly install JDK 11 (or newer) on GitHub Actions runners using the
setup-java
action, instead of relying on the java version that happened to be installed on the runner.Googlers can see b/233751585 for details.