Repository navigation
test(rust): rename test manifest to avoid conflicts with local drivers - #4946
Merged
lidavidm merged 1 commit intoOct 27, 2026
Merged
Conversation
amoeba
changed the title
lidavidm
approved these changes
Oct 25, 2026
Member
|
Something broke in CI, let me see... |
Member
amoeba
force-pushed
the
fix/rust-driver-manager-manifest-conflict
branch
from
October 26, 2026 21:31
209a860 to
33f924b
Compare
Member
Author
|
Rebased to fix conda issue. |
Member
Author
|
I think we can rebase this after the bump versions PR is merged to fix the JS errors. |
lidavidm
approved these changes
Oct 26, 2026
amoeba
force-pushed
the
fix/rust-driver-manager-manifest-conflict
branch
from
October 27, 2026 18:32
33f924b to
8756ec3
Compare
Member
Author
|
Rebased, watching CI. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Edits the Rust driver manager tests that previously looked for a driver manifest named sqlite.toml to use a path less likely to conflict with user and system level versions of the sqlite driver. This is basically the same thing as was fixed in 22f0f4a.
To reproduce the failure, run
dbc install sqliteand then run the driver manager tests.