8000 chore: test fix. by Genesis929 · Pull Request #1121 · googleapis/python-bigquery-dataframes · GitHub
[go: up one dir, main page]

Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion tests/system/small/test_session.py
Original file line number Diff line number Diff line change
Expand Up @@ -399,7 +399,7 @@ def test_read_gbq_twice_with_same_timestamp(session, penguins_table_id):
)
def test_read_gbq_on_linked_dataset_warns(session, source_table):
with warnings.catch_warnings(record=True) as warned:
session.read_gbq(source_table)
session.read_gbq(source_table, use_cache=False)
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 know why a cached read will trigger one extra warning?

Copy link
Collaborator Author
@Genesis929 Genesis929 Oct 29, 2024

Choose a reason for hiding this comment

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

If a table is read multiple times in the same session, there will be warning messages except for the first read. And there are two tests that include step to read this table, most likely in the same session. That I think is the cause.

Check b/375664942 for details.

assert len(warned) == 1
assert warned[0].category == bigframes.exceptions.TimeTravelDisabledWarning

Expand Down
0