Skip to content

Conversation

@calpeyser
Copy link
Contributor

Re-submission for PR #3324.

@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Aug 14, 2017
@calpeyser calpeyser changed the title Fix retry RPC retries (resubmission) Aug 14, 2017
@calpeyser
Copy link
Contributor Author

@dhermes please take a look. Is there anything I should do outside of regular CI to run the tests that failed the last time around?

@dhermes
Copy link
Contributor

dhermes commented Aug 14, 2017

@calpeyser Sending a PR from your remote will skip the system tests, which is partly why I kept the change around in a branch on the GoogleCloudPlatform remote.

So before we merge this, we should push this branch to the GoogleCloudPlatform remote so the system tests can be run. (FWIW, I have yet to review, though someone else can sign off, I'm not the only one with authority here.)

"""
request_pb = _create_row_request(
self.name, start_key=start_key, end_key=end_key, filter_=filter_,
limit=limit, end_inclusive=end_inclusive)

This comment was marked as spam.

This comment was marked as spam.

@calpeyser calpeyser changed the base branch from master to pr-3324-to-fix August 15, 2017 16:38
@calpeyser
Copy link
Contributor Author

calpeyser commented Aug 15, 2017

@dhermes PTAL. Would it be easier to PR against an empty branch, so as not to deal with the backlog of commits? I don't seem to have the privileges to rebase this branch from master.

Looking at the test logs, it seems that the system tests are still being skipped.

@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that they're okay with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

@googlebot googlebot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Aug 15, 2017
@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that they're okay with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

@dhermes dhermes changed the base branch from pr-3324-to-fix to master August 15, 2017 17:41
@dhermes
Copy link
Contributor

dhermes commented Aug 15, 2017

@calpeyser I changed the base back to master. I'll just manually push your branch to the other remote so CI can run in parallel with this.

@dhermes
Copy link
Contributor

dhermes commented Aug 15, 2017

@mbrukman
Copy link
Contributor

@calpeyser – looks like the build/test failed on CircleCI; could you take a look, please?

@googlebot
Copy link

CLAs look good, thanks!

@googlebot googlebot added cla: yes This human has signed the Contributor License Agreement. and removed cla: no This human has *not* signed the Contributor License Agreement. labels Aug 16, 2017
@calpeyser
Copy link
Contributor Author

@dhermes can you patch the change "encode -> decode for bytestring in bigtable system test" into the branch on the remote? The system tests don't seem to run here.

The current failure is in "Update the docs", and seems unrelated to this change.

@calpeyser
Copy link
Contributor Author

@dhermes ping on pushing the lastest commit to the remote branch so we can run the system tests.

@dhermes
Copy link
Contributor

dhermes commented Aug 21, 2017

Sorry, doing it now!

@dhermes
Copy link
Contributor

dhermes commented Aug 21, 2017

(Email is a crappy task list, my bad.)

@dhermes
Copy link
Contributor

dhermes commented Aug 21, 2017

New build: https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/2951
Non-system-test red build: https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/2917

@calpeyser I see the docs breakage in the last build, you should probably rebase against master due to some moves / nox config changes?

@dhermes
Copy link
Contributor

dhermes commented Aug 21, 2017

@calpeyser The system tests failed in the build. Do they pass when you run them locally? If you haven't run them locally, is there anything I can do to help you get them running?

$ pip install --upgrade nox-automation
$ cd /path/to/your/git-checkout/of/google-cloud-python/
$ cd bigtable/
$ nox -s "system_tests(python_version='2.7')"
$ nox -s "system_tests(python_version='3.6')"

@calpeyser
Copy link
Contributor Author

@garye what do you think?

@garye
Copy link
Contributor

garye commented Oct 31, 2017

LGTM! Just need @dhermes, @lukesneeringer or someone from the team to pull the trigger I think.

@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this State. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

@googlebot googlebot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Nov 10, 2017
@tseaver tseaver added cla: yes This human has signed the Contributor License Agreement. and removed cla: no This human has *not* signed the Contributor License Agreement. labels Nov 10, 2017
@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this State. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

@googlebot googlebot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Nov 14, 2017
@calpeyser
Copy link
Contributor Author

@tseaver - I've fixed the issues with the merge above - can this PR be merged?

@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this State. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

@tseaver tseaver merged commit 5a0e549 into googleapis:master Nov 15, 2017
@dhermes
Copy link
Contributor

dhermes commented Nov 15, 2017

https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4249

I think this may need to be reverted

@dhermes
Copy link
Contributor

dhermes commented Nov 16, 2017

@calpeyser @garye Here is another (albeit less severe) failure:

https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4256

There have been no other builds on master since the previous failure.


It's worth noting that we have other packages with tests that are flaky (which we tolerate mostly due to lack of developer resources), but this one seems to be a preventable flakiness.

@dhermes
Copy link
Contributor

dhermes commented Nov 16, 2017

I'm just going to collect a list of broken builds here (for debugging purposes):

  1. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4249
  2. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4256
  3. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4262
  4. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4277
  5. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4278
  6. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4290
  7. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4323
  8. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4330
  9. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4334
  10. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4337
  11. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4338
  12. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4349
  13. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4361
  14. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4399
  15. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4404
  16. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4407
  17. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4408
  18. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4413
  19. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4417
  20. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4419
  21. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4421
  22. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4423
  23. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4432
  24. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4439
  25. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4452
  26. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4458
  27. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4459
  28. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4468
  29. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4470
  30. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4472
  31. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4474
  32. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4478
  33. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4501
  34. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4506
  35. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4508
  36. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4513
  37. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4517
  38. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4524
  39. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4526
  40. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4527
  41. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4528
  42. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4529
  43. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4535
  44. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4536
  45. https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4540

I may edit it as more occur / if more occur.

@dhermes
Copy link
Contributor

dhermes commented Nov 21, 2017

@calpeyser @garye Please weigh in here. I am leaning towards reverting this PR (we need our builds to not fail).

@igorbernstein2
Copy link

I can try to fix this tomorrow. After a quick look, I think that the issue is that the test_retry test never cleans up the BIGTABLE_EMULATOR_HOST env var, causing the rest of the tests to connect to a dead port

@dhermes
Copy link
Contributor

dhermes commented Nov 21, 2017

Thanks @igorbernstein2. I'm happy to help (e.g. if you're unfamiliar with unittest.mock.patch).

@calpeyser
Copy link
Contributor Author

This breakage certainly looks related to this change. @igorbernstein2, thanks a ton - I think you're right about the env var.

dhermes added a commit to dhermes/google-cloud-python that referenced this pull request Dec 4, 2017
dhermes added a commit that referenced this pull request Dec 4, 2017
dhermes added a commit that referenced this pull request Dec 4, 2017
parthea pushed a commit that referenced this pull request Nov 22, 2025
parthea pushed a commit that referenced this pull request Nov 22, 2025
This reverts commit 1c699f36584d8c507118dae9ab8a2a31bc951ce6 / PR #3811.
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: no This human has *not* signed the Contributor License Agreement. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants