Skip to content

Conversation

rahul2393
Copy link
Contributor

Run the GraalVM integration tests on the emulator instead of production to speed up builds.

@rahul2393 rahul2393 requested review from a team as code owners July 4, 2024 05:53
@product-auto-label product-auto-label bot added the size: s Pull request size is small. label Jul 4, 2024
@rahul2393 rahul2393 requested a review from olavloite July 4, 2024 05:53
@product-auto-label product-auto-label bot added the api: spanner Issues related to the googleapis/java-spanner API. label Jul 4, 2024
@rahul2393 rahul2393 force-pushed the run-native-integration-tests-on-emulator branch from 83fd7e9 to d9d913d Compare July 4, 2024 05:54
Comment on lines +53 to +56
echo "Starting emulator"
export SPANNER_EMULATOR_HOST=localhost:9010
docker pull gcr.io/cloud-spanner-emulator/emulator
docker run -d --rm --name spanner-emulator -p 9010:9010 -p 9020:9020 gcr.io/cloud-spanner-emulator/emulator
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: How about moving this with in the switch case below?

graalvm)
# Run Unit and Integration Tests with Native Image

I understand that there will be code duplication. But just thinking that this will give clarity to someone looking at graalvm that it runs on emulator and not real backend.

@olavloite olavloite added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Aug 6, 2024
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Aug 6, 2024
@olavloite olavloite merged commit fedac3f into main Aug 6, 2024
@olavloite olavloite deleted the run-native-integration-tests-on-emulator branch August 6, 2024 18:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: spanner Issues related to the googleapis/java-spanner API. size: s Pull request size is small.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants