What happened?
When I verified the ADBC 24 release, the driver manager tests initially failed, because I had a driver or driver manifest in my environment that interfered with the tests. We should remedy this e.g. by using obscure names for all drivers, driver manifests, and connection profiles in the tests, or by erroring early with a useful message if the user environment or the conda environment is contaminated with files that will interfere with the tests.
How can we reproduce the bug?
dbc install sqlite --level user
./dev/release/verify-release-candidate.sh 24 2
Fails with:
The following tests FAILED:
4 - adbc-driver-manager-test (Failed) driver-manager unittest
Errors while running CTest
Solved by:
dbc uninstall sqlite --level user
Environment/Setup
conda
macOS
What happened?
When I verified the ADBC 24 release, the driver manager tests initially failed, because I had a driver or driver manifest in my environment that interfered with the tests. We should remedy this e.g. by using obscure names for all drivers, driver manifests, and connection profiles in the tests, or by erroring early with a useful message if the user environment or the conda environment is contaminated with files that will interfere with the tests.
How can we reproduce the bug?
Fails with:
Solved by:
Environment/Setup
conda
macOS