Add config: one_schema_per_test.json #19059
Merged
+128
−2
Conversation
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
|
Thanks! |
krlmlr
added a commit
to duckdb/duckdb-r
that referenced
this pull request
Sep 29, 2025
Avoid throwing on unset extension setting (duckdb/duckdb#19117) Fix example syntax in `variant_typeof()` function (duckdb/duckdb#18977) Bump httpfs (duckdb/duckdb#19104) Moved test data into testing dir (duckdb/duckdb#19102) Change bucket name for core extensions (duckdb/duckdb#19083) Add config: one_schema_per_test.json (duckdb/duckdb#19059)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Follow up from #19056, now you can do (if you want):
and you will end up with a DuckDB database at
./new_dir/unittest_all.dbthat is just short of 750MB.The added configuration is currently NOT run in CI.