You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the pandas test suite with ADBC drivers users currently see this output:
pandas/tests/io/test_sql.py .........NOTICE: table "test_frame" does not exist, skipping
.........FNOTICE: table "test_frame" does not exist, skipping
x.........NOTICE: table "test_frame" does not exist, skipping
..........NOTICE: table "test_frame" does not exist, skipping
..........NOTICE: table "test_frame" does not exist, skipping
..........NOTICE: table "test_frame" does not exist, skipping
..........NOTICE: table "test_frame" does not exist, skipping
..........NOTICE: table "test_frame" does not exist, skipping
...................xNOTICE: table "test_frame" does not exist, skipping
x........WARNING: there is no transaction in progress
..........WARNING: there is no transaction in progress
.....................NOTICE: table "test_frame" does not exist, skipping
.........xNOTICE: table "test_frame" does not exist, skipping
x...............xNOTICE: table "test_frame" does not exist, skipping
x.....................................................................................................................................................................ss..............x...................................................................x..................................................................F.............................................................................
Would be nice if those didn't appear downstream
The text was updated successfully, but these errors were encountered:
I'm just going to suppress it for now (perhaps with an env var to allow it through), with the idea that somewhere between #735 and #924 we'll expose it in the actual driver logs
lidavidm
added a commit
to lidavidm/arrow-adbc
that referenced
this issue
Sep 1, 2023
When running the pandas test suite with ADBC drivers users currently see this output:
Would be nice if those didn't appear downstream
The text was updated successfully, but these errors were encountered: