bvolpato opened a new pull request, #26840:
URL: https://github.com/apache/datafusion/pull/26840

   > [!IMPORTANT]
   >
   > **Fork CI setup:** For pull requests from a fork to `main`, enable 
workflows in your fork's **Actions** tab before you push.
   > See the [fork CI setup 
guide](https://datafusion.apache.org/contributor-guide/#pull-requests-from-forks).
   
   ## Which issue does this PR close?
   
   Part of #13813.
   
   ## Rationale for this change
   
   The zero-merge-reservation and runtime-memory-limit tests each sort 10M 
generated rows to check that spilling occurs. Both also discard the collection 
result, so spilling alone can satisfy their assertions even if execution fails.
   
   ## What changes are included in this PR?
   
   Use smaller inputs that still exceed the configured memory budgets. Retain 
the parallel zero-reservation configuration and use one partition for 
predictable pressure in the runtime `SET` test.
   
   Require collection to succeed, check the complete output row count, and 
retain the positive spill assertions.
   
   ## What is the testing strategy for this PR?
   
   Focused `ci`-profile runs changed from 10.4s to 0.84s for zero merge 
reservation and from 18.7s to 0.54s for the runtime memory limit. These are 
single runs on a shared Linux host. Both checks verify successful complete 
output and actual spilling.
   
   Formatting, all-target/all-feature Clippy, and the extended workspace suite 
passed. Full workspace validation included the RSS sampling prerequisite 
already carried in #26445.
   
   ## Are there any user-facing changes?
   
   None. This changes test fixtures and assertions only.
   
   AI-assisted contribution.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to