Uh oh!
There was an error while loading. Please reload this page.
Bigtable: Add ability to run tests against direct path - #5756
Conversation
* Reorganize failsafe config to have a separate execution for each test integration test target * Move each test integration target into it's own profile (keeping the emulator tests on by default) * Fork the ProdEnv for direct path environment
igorbernstein2
commented
Jul 18, 2019
This is currently broken because of The bigtable gapic yaml needs to be updated with correct rpc timeouts. I have a CL out that fixes all of the RPC timeouts, but can't be merged until googleapis/gapic-generator#2878 is merged |
Codecov Report
@@ Coverage Diff @@## master #5756 +/- ##
============================================
+ Coverage 47.17% 47.17% +<.01%
Complexity 25130 25130 ============================================
Files 2389 2389 Lines 259836 259836 Branches 29417 29417 ============================================
+ Hits 122585 122586 +1 + Misses 128321 128320 -1
Partials 8930 8930
Continue to review full report at Codecov.
|
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
igorbernstein2
commented
Jul 18, 2019
Looks like emulator tests are failing because cbt emulator doesn't exist in kokoro. |
This was a bug introduced in googleapis#5756. When integration profiles were introduced, I forgot to remove the test from the default execution of the failsafe plugin. The new way integration tests are run are via profile activation: by default the bigtable-emulator-it profile is active.
* Bigtable: Add ability to run tests against direct path * Reorganize failsafe config to have a separate execution for each test integration test target * Move each test integration target into it's own profile (keeping the emulator tests on by default) * Fork the ProdEnv for direct path environment * update docs * cherrypick googleapis#5762 * include port in const * fix emulator system prop * make sure to download emulator before running the bigtable integration tests * fix kokoro cmd line * fix continuous & nightly jobs as well * wrokaround flakes due to jdk bug
googleapis#5955) This was a bug introduced in googleapis#5756. When integration profiles were introduced, I forgot to remove the test from the default execution of the failsafe plugin. The new way integration tests are run are via profile activation: by default the bigtable-emulator-it profile is active.
NOTE: please review #5762 first. This PR includes changes from there
Please note that the directpath tests are not enabled in kokoro yet