Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: Travis failure in master because of GBQ table #30470

Closed
datapythonista opened this issue Dec 25, 2019 · 10 comments · Fixed by #30478
Closed

CI: Travis failure in master because of GBQ table #30470

datapythonista opened this issue Dec 25, 2019 · 10 comments · Fixed by #30478
Labels
CI Continuous Integration
Milestone

Comments

@datapythonista
Copy link
Member

Looks like there is a problem with GBQ. A test is finding that a table already exists. It's making Travis fail master. Didn't check in detail, the log is here: https://travis-ci.org/pandas-dev/pandas/jobs/629453901#L2297

@tswast mind having a look?

CC: @jreback

@datapythonista datapythonista added CI Continuous Integration IO Google labels Dec 25, 2019
@jreback
Copy link
Contributor

jreback commented Dec 25, 2019

#30447 could have broken this

@datapythonista if you want to xfail this for now would be great.

@jreback jreback added this to the 1.0 milestone Dec 25, 2019
@alimcmaster1
Copy link
Member

Yep looks like the table added isn't removed in the teardown_class

In test_gbq.py :
destination_table = DESTINATION_TABLE + "2"

I can potentially take a look

@jreback
Copy link
Contributor

jreback commented Dec 26, 2019

ideally should fixtureze these tables to avoid this

@jreback
Copy link
Contributor

jreback commented Dec 26, 2019

hmm this is still running this test (maybe there were 2) https://travis-ci.org/pandas-dev/pandas/jobs/629507853

This was referenced Dec 26, 2019
@charlesdong1991
Copy link
Member

charlesdong1991 commented Dec 26, 2019

ahh, sorry about CI failure! I just take a look, and the test failed when if_exists=='fail'. And as i looked at pandas-gbq and found out the problem.

From pandas.to_gbq documentation (https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.to_gbq.html), when if_exists=='fail', it says If table exists, do nothing., so in the test, i leave the table size as is.
But in pandas_gbq documentation (https://pandas-gbq.readthedocs.io/en/latest/writing.html#writing-to-an-existing-table), it says when if_exists=='fail', should raise TableCreationError and this is why CI failed.

I did not double check the documentation from pandas_gbq when working on it, and somehow, this error did not show up in my local and PR test, so was overlooked. Very sorry about that.

changing the result to TableCreationError for fail should fix the problem

@datapythonista @jreback @alimcmaster1

could be good to change the documentation as well in #30478 to make the documentation clearer for fail.

@datapythonista
Copy link
Member Author

Can you open a PR with this @charlesdong1991 ? Thanks!

@charlesdong1991
Copy link
Member

yeah, of course, but i saw a PR related to it was already opened by @alimcmaster1

Or do you mean that you want a PR for doc change? @datapythonista

@datapythonista
Copy link
Member Author

Sorry, didn't see the PR. But yes, creating one for the doc changes you propose sounds good.

@charlesdong1991
Copy link
Member

sure!

@alimcmaster1
Copy link
Member

Our docs are a copy of the gbq ones, i've updated the pandas side here. Would be good to do the same in pandas_gbq.

Thinking we should maybe restore a little documentation around this. Since these tests do not run on PRs. (Only master)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous Integration
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants