Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

BigQuery: Use configurable bucket name for GCS samples data in systems tests.#8783

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
tswast merged 3 commits intogoogleapis:masterfromtswast:issue8550-bq-vpc-sc-tests
Jul 29, 2019

Conversation

@tswast
Copy link
Contributor

This allows the VPC-SC team to use their private mirror which is within
the security boundary when testing BigQuery VPC-SC support.

Closes#8550.

This allows the VPC-SC team to use their private mirror which is withinthe security boundary when testing BigQuery VPC-SC support.
@tswasttswast added testing api: bigqueryIssues related to the BigQuery API. type: processA process-related concern. May include testing, release, or the like. labelsJul 25, 2019
@tswasttswast requested a review froma teamJuly 25, 2019 18:32
@googlebotgooglebot added the cla: yesThis human has signed the Contributor License Agreement. labelJul 25, 2019
@tswasttswast requested a review fromshollymanJuly 25, 2019 18:33
# The VPC-SC team maintains a mirror of the GCS bucket used for code
# samples. The public bucket crosses the configured security boundary.
# See: https://github.com/googleapis/google-cloud-python/issues/8550
SAMPLES_BUCKET=os.environ.get("GCLOUD_TEST_SAMPLES_BUCKET","cloud-samples-data")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Do we need to updatenoxfile.py to set this value in the environment?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

No, the default ofcloud-samples-data is fine for our purposes. The VPC-SC team has a separate Kokoro (or maybe something similar?) config where they'll set the necessary environment variable.

@tswast
Copy link
ContributorAuthor

___________________ test_bq_to_arrow_array_w_special_floats ____________________module_under_test = <module 'google.cloud.bigquery._pandas_helpers' from '/tmpfs/src/github/google-cloud-python/bigquery/google/cloud/bigquery/_pandas_helpers.py'>    @pytest.mark.skipif(pandas is None, reason="Requires `pandas`")    @pytest.mark.skipif(pyarrow is None, reason="Requires `pyarrow`")    def test_bq_to_arrow_array_w_special_floats(module_under_test):        bq_field = schema.SchemaField("field_name", "FLOAT64")        rows = [float("-inf"), float("nan"), float("inf"), None]        series = pandas.Series(rows, dtype="object")        arrow_array = module_under_test.bq_to_arrow_array(series, bq_field)        roundtrip = arrow_array.to_pylist()        assert len(rows) == len(roundtrip)        assert roundtrip[0] == float("-inf")>       assert roundtrip[1] != roundtrip[1]  # NaN doesn't equal itself.E       assert None != None

failure is unrelated. I think it's a behavior change / regression frompyarrow.

@tseaver
Copy link
Contributor

@tswast How should we track that regression? All BigQuery CI is b0rked ATM.

@tswast
Copy link
ContributorAuthor

@tswast How should we track that regression? All BigQuery CI is b0rked ATM.

Let's pin topyarrow==0.13.0 in the noxfile until I can reproduce the regression and file an issue on the Apache Arrow JIRA.

@tswast
Copy link
ContributorAuthor

Sent#8784.

@tswasttswast merged commitbbe686d intogoogleapis:masterJul 29, 2019
@tswasttswast deleted the issue8550-bq-vpc-sc-tests branchJuly 29, 2019 16:36
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@shollymanshollymanshollyman approved these changes

+1 more reviewer

@tseavertseavertseaver left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

api: bigqueryIssues related to the BigQuery API.cla: yesThis human has signed the Contributor License Agreement.testingtype: processA process-related concern. May include testing, release, or the like.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

BigQuery:test_create_routine test fails on VPC-SC tests

4 participants

@tswast@tseaver@shollyman@googlebot

[8]ページ先頭

©2009-2025 Movatter.jp