wiedld commented on PR #17944:
URL: https://github.com/apache/datafusion/pull/17944#issuecomment-3373814160
We have a CI failure, in which the error message (and running it locally for
me) correctly expects no disk spilling. Whereas it fails in CI since it somehow
doesn't have the no-spill configured right in CI?
```
failures:
---- memory_limit::sort_merge_join_no_spill stdout ----
thread 'memory_limit::sort_merge_join_no_spill' panicked at
datafusion/core/tests/memory_limit/mod.rs:916:25:
Can not find expected in actual.
Expected:
Execution error: Additional allocation failed for SMJStream[partition=0]
with top memory consumers (across reservations) as:
SMJStream[partition=0]#ID(can spill: false) consumed x B, peak x B.
Error: Failed to allocate additional x KB for SMJStream[partition=0] with x
B already allocated for this reservation - x B remain available for the total
pool. Disk spilling disabled.
Actual:
Execution error: Additional allocation failed for SMJStream[partition=0]
with top memory consumers (across reservations) as:
SMJStream[partition=0]#ID(can spill: false) consumed x B, peak x B.
Error: Failed to allocate additional x KB for SMJStream[partition=0] with x
B already allocated for this reservation - x B remain available for the total
pool
```
I'll take a look at this tmrw.
--
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]
