bigtable: system tests #1461
Merged
bigtable: system tests #1461
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stephenplusplus
added
don't merge
api: bigtable
googlebot
added
the
cla: yes
Closed
Mocha will run blocks, even if they are skipped. This was causing errors to be thrown if the contributor didn't have the Bigtable env vars set
stephenplusplus
force-pushed
the
spp--bigtable-system-test
branch
from
0889c70 to
08eeb90
Compare
|
Changes Unknown when pulling 08eeb90 on stephenplusplus:spp--bigtable-system-test into * on GoogleCloudPlatform:master*. |
stephenplusplus
added a commit
to stephenplusplus/gcloud-node
that referenced
this pull request
Aug 23, 2016
Mocha will run blocks, even if they are skipped. This was causing errors to be thrown if the contributor didn't have the Bigtable env vars set
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mocha will run blocks, even if they are skipped. This was causing errors to be thrown if the contributor didn't have the Bigtable env vars set.