Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Test Fix] Add noforcestorage to in-memory tests #14016

Merged
merged 2 commits into from
Sep 19, 2024

Conversation

taniabogatsch
Copy link
Contributor

@duckdb-draftbot duckdb-draftbot marked this pull request as draft September 18, 2024 15:40
@taniabogatsch
Copy link
Contributor Author

@taniabogatsch taniabogatsch marked this pull request as ready for review September 18, 2024 15:40
@Mytherin Mytherin merged commit 58e511c into duckdb:main Sep 19, 2024
27 of 28 checks passed
@Mytherin
Copy link
Collaborator

Thanks!

@taniabogatsch taniabogatsch deleted the block-size branch September 19, 2024 08:31
github-actions bot pushed a commit to duckdb/duckdb-r that referenced this pull request Sep 27, 2024
Fix duckdb/duckdb#14020: fix off-by-one in RLE compression: avoid flushing when last_seen_count == 0 which can happen if a column has exactly 2^16 (65535) repeated values (duckdb/duckdb#14030)
[Test Fix] Add noforcestorage to in-memory tests (duckdb/duckdb#14016)
github-actions bot added a commit to duckdb/duckdb-r that referenced this pull request Sep 27, 2024
Fix duckdb/duckdb#14020: fix off-by-one in RLE compression: avoid flushing when last_seen_count == 0 which can happen if a column has exactly 2^16 (65535) repeated values (duckdb/duckdb#14030)
[Test Fix] Add noforcestorage to in-memory tests (duckdb/duckdb#14016)

Co-authored-by: krlmlr <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants