ci: use emulator for Spanner and Bazel#6812
Conversation
|
Google Cloud Build Logs
ℹ️ NOTE: Kokoro logs are linked from "Details" below. |
|
Google Cloud Build Logs
ℹ️ NOTE: Kokoro logs are linked from "Details" below. |
Codecov Report
@@ Coverage Diff @@
## main #6812 +/- ##
==========================================
- Coverage 95.51% 95.02% -0.49%
==========================================
Files 1262 1262
Lines 113094 113094
==========================================
- Hits 108026 107473 -553
- Misses 5068 5621 +553
Continue to review full report at Codecov.
|
| --test_env="GOOGLE_CLOUD_CPP_AUTO_RUN_EXAMPLES=yes" \ | ||
| --test_env="GOOGLE_CLOUD_CPP_EXPERIMENTAL_LOG_CONFIG=lastN,100,WARNING" \ | ||
| --test_env="GOOGLE_CLOUD_CPP_ENABLE_TRACING=rpc,rpc-streams" \ | ||
| --test_env="GOOGLE_CLOUD_CPP_TRACING_OPTIONS=truncate_string_field_longer_than=512" \ |
There was a problem hiding this comment.
The cmake version sets GOOGLE_CLOUD_CPP_SPANNER_SLOW_INTEGRATION_TESTS="instance,backup", which I imagine is OK because the emulator doesn't actually support the slow operations. Either way, we should probably make in the bazel/cmake invocations match as much as possible.
|
PTAL, I made some additional changes to ensure the Bazel caches the test results. |
|
Google Cloud Build Logs
ℹ️ NOTE: Kokoro logs are linked from "Details" below. |
Avoids some flakes by using the emulator. We still have
some builds hitting production, mostly macOS and Windows.
This change is