Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@igorbernstein2
Copy link

@igorbernstein2 igorbernstein2 commented Jul 16, 2019

NOTE: please review #5762 first. This PR includes changes from there

  • 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

Please note that the directpath tests are not enabled in kokoro yet

* 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 igorbernstein2 added the api: bigtable Issues related to the Bigtable API. label Jul 16, 2019
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Jul 16, 2019
@igorbernstein2 igorbernstein2 added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 17, 2019
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 17, 2019
@igorbernstein2
Copy link
Author

This is currently broken because of
googleapis/gax-java#745

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
Copy link

codecov bot commented Jul 18, 2019

Codecov Report

Merging #5756 into master will increase coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@             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
Impacted Files Coverage Δ Complexity Δ
...ain/java/com/google/cloud/pubsub/v1/Publisher.java 89.89% <0%> (+0.34%) 40% <0%> (ø) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4a95f17...42ee5e5. Read the comment docs.

kolea2
kolea2 previously requested changes Jul 18, 2019
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 18, 2019
@igorbernstein2
Copy link
Author

Looks like emulator tests are failing because cbt emulator doesn't exist in kokoro.
#5769 should fix that

@igorbernstein2 igorbernstein2 added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 19, 2019
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 19, 2019
@igorbernstein2 igorbernstein2 dismissed kolea2’s stale review July 19, 2019 17:52

All feedback should addressed

@igorbernstein2 igorbernstein2 merged commit 76062ba into googleapis:master Jul 19, 2019
@igorbernstein2 igorbernstein2 deleted the directpath branch July 19, 2019 17:52
igorbernstein2 added a commit to igorbernstein2/google-cloud-java that referenced this pull request Aug 1, 2019
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.
igorbernstein2 added a commit that referenced this pull request Aug 1, 2019
#5955)

This was a bug introduced in #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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: bigtable Issues related to the Bigtable API. cla: yes This human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants