ARROW-15438: [Python] Flaky test test_write_dataset_max_open_files #12263
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.
The test could fail when writing due to a race condition. If the batches were delivered
AAAAABBBBBCCCCC...
then by the time we need to close a file to make space we can close an already completed file (and so we won't have to open up a new one later) and we end up with 5 files for 5 partitions.Adding
use_threads=False
to thewrite_dataset
call was not sufficient. Thearrow::dataset::FileSystemDataset::Write
method was always using the CPU executor for the exec plan. In other scanner methods we base the CPU executor on the scan options (nullptr
ifscan_options->use_threads
isfalse
). Making both of these changes together seems to make the test reliably pass.