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
In the output of all these step we don't see adbc-driver-manager-test. Is this normal or am I misunderstanding something?
I've stumbled upon this while debugging an issue with the Rust implementation and it might be related to using the SQLite driver through the driver manager on Windows (though I can't reproduce the issue on my local Windows 11...)
How can we reproduce the bug?
No response
Environment/Setup
No response
The text was updated successfully, but these errors were encountered:
Windows doesn't get much attention since I don't think many contributors have a dedicated Windows machine, and the Microsoft developer VM expires really quickly
What happened?
It looks like tests for the driver manager are not executed on Windows during CI runs.
Here are a few concrete recent examples:
In the output of all these step we don't see
adbc-driver-manager-test
. Is this normal or am I misunderstanding something?I've stumbled upon this while debugging an issue with the Rust implementation and it might be related to using the SQLite driver through the driver manager on Windows (though I can't reproduce the issue on my local Windows 11...)
How can we reproduce the bug?
No response
Environment/Setup
No response
The text was updated successfully, but these errors were encountered: