[Chore] Tidy test configs#18426
Merged
Mytherin merged 2 commits intoduckdb:v1.3-ossivalisfrom Jul 29, 2025
Merged
Conversation
Contributor
Author
|
I just now noticed that we use I'll try to update these tests and fix the storage runs. |
Collaborator
|
Thanks! |
github-actions bot
pushed a commit
to duckdb/duckdb-r
that referenced
this pull request
Jul 30, 2025
[Fix] Reset segment memory when initialising new Prefix (duckdb/duckdb#18441) [Chore] Tidy test configs (duckdb/duckdb#18426)
github-actions bot
added a commit
to duckdb/duckdb-r
that referenced
this pull request
Jul 30, 2025
[Fix] Reset segment memory when initialising new Prefix (duckdb/duckdb#18441) [Chore] Tidy test configs (duckdb/duckdb#18426) Co-authored-by: krlmlr <krlmlr@users.noreply.github.com>
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
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.
While looking into https://github.com/duckdblabs/duckdb-internal/issues/5207, I noticed that the descriptions and test config files had already diverged a bit and decided to unify them.