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

   ## Which issue does this PR close?
   
   N/A - follow-up maintenance.
   
   ## Rationale for this change
   
   The sqllogictest runner runs test files in parallel but each file
   sequentially, so it prioritizes known long-running files to run first to
   minimize total wall-clock time. This list was last set in #20656.
   
   The relative timings have since shifted. Running with the
   `--timing-summary` flag now reports a different ordering of the longest
   files, with `nested_loop_join_spill.slt` having become the longest by a
   fair margin:
   
   ```text
   $ cargo test --profile=ci --test sqllogictests -- --timing-summary
   Per-file elapsed summary (deterministic):
     1.    5.437s  nested_loop_join_spill.slt
     2.    3.471s  push_down_filter_regression.slt
     3.    3.458s  aggregate.slt
     4.    3.065s  joins.slt
     5.    2.852s  aggregate_skip_partial.slt
     6.    2.832s  imdb.slt
     7.    2.453s  window.slt
     8.    1.831s  group_by.slt
     9.    1.282s  clickbench.slt
    10.    1.055s  datetime/timestamps.slt
    11.    0.994s  array/array_has.slt
    12.    0.840s  cte.slt
    13.    0.748s  sort_pushdown.slt
    14.    0.714s  push_down_filter_parquet.slt
    15.    0.668s  projection_pushdown.slt
   ```
   
   ## What changes are included in this PR?
   
   - Update `TEST_PRIORITY_ENTRIES` in 
`datafusion/sqllogictest/src/test_file.rs`
     to match the latest `--timing-summary` ordering, promoting
     `nested_loop_join_spill.slt` to the front and adding several newly
     long-running files.
   - Update the example output in the accompanying doc comment.
   
   ## Are these changes tested?
   
   Yes - the existing `prioritized_files_are_first` unit test passes.
   
   ## Are there any user-facing changes?
   
   No.
   
   Follow-up to #20656.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
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