Repository navigation
ci(linux): fit the Devel Flatpak on the runner disk and fix two package builder test timeouts - #4295
Merged
Merged
Conversation
datlechin
enabled auto-merge (squash)
November 15, 2026 14:08
…B name, which DuckDB opens in time
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.
Summary
CARGO_INCREMENTAL=0andCARGO_PROFILE_DEV_DEBUG=line-tables-onlyin the build options.debug/deps52 GB,debug/incremental18 GB) against 76 GB free on Azure and 79 GB on AWS. 4 of 5 probe jobs ran out, on main and on b451ff2, before fix(core): bound what a SQLite or DuckDB catalog read holds #4287; the one pass bottomed at 1.9 GB free. The nightly of 2026-11-14 failed the same way.catalog_memorytest: the crafted child has 60 keys and a 640 KiB name instead of 600 keys and 64 KiB. Each key DuckDB adds to the parent copies every earlier one, so the open cost keys squared times name, and it passed the 10 s connect timeout on the package builders (Debian resolute here, Debian stonking and Fedora 44 on main af5869a). The reads it checks cost keys times name, the same 39 MB as before.a_tool_call_the_app_never_answers_stops_at_its_deadline: the handshake, which the test server answers itself, gets the usual 15 s bound and only the tool call keeps 300 ms. On the Fedora 45 package builder the handshake took over 300 ms and the test failed in setup (NoAnswer { seconds: 0 }is 300 ms rounded down).Test plan
linux / Flatpak Devel (x86_64)on this PR, run three times.catalog_memorylocally: the file opens in 0.7 s against 1.8 to 2.3 s and is created in 0.9 s against 5 to 6 s; the test takes 2.5 s against 8.2 s. With the constraint estimate disabled it still fails, holding 64 MB for the keys intonamed_parent.catalog_memorytakes 5.5 and 6.2 s against 17.7 to 24 s before.verify.sh core tablepro-cli client::tests: 4 of 4 pass.