-
Notifications
You must be signed in to change notification settings - Fork 125
tests.system.test_read_gbq: test_default_dtypes[issue365-extreme-datetimes-False] failed #624
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
tests.system.test_read_gbq: test_default_dtypes[issue365-extreme-datetimes-False] failed #624
Comments
Looks like this issue is flaky. 😟 I'm going to leave this open and stop commenting. A human should fix and close this. When run at the same commit (1dca732), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge). |
1 similar comment
Looks like this issue is flaky. 😟 I'm going to leave this open and stop commenting. A human should fix and close this. When run at the same commit (1dca732), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge). |
Oops! Looks like this issue is still flaky. It failed again. 😬 I reopened the issue, but a human will need to close it again. commit: 1dca732 Test outputread_gbq = functools.partial(, project_id='precise-truck-742', credentials=) query = '\nSELECT\n dates.row_num AS row_num,\n date_col,\n datetime_col,\n timestamp_col\nFROM\n UNNEST([\n STRUCT(...dates`.row_num = `datetimes`.row_num\n AND `dates`.row_num = `timestamps`.row_num\nORDER BY row_num ASC\n ' expected = row_num ... timestamp_col 0 1 ... 0001-01-01 00:00:00+00:00 1 2 ... 9999-12-31 23:59:59.999999+00:00 2 3 ... 2262-04-11 23:47:16.854776+00:00 |
This test failed!
To configure my behavior, see the Flaky Bot documentation.
If I'm commenting on this issue too often, add the
flakybot: quiet
label andI will stop commenting.
commit: 1dca732
buildURL: Build Status, Sponge
status: failed
Test output
The text was updated successfully, but these errors were encountered: