Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix flaky test test_fuzz_async_reader_selection #2656

Merged
merged 1 commit into from
Sep 6, 2022

Conversation

thinkharderdev
Copy link
Contributor

Which issue does this PR close?

Closes #.

Rationale for this change

Fixes flaky fuzz test for row selection. Was generating random row selections with row_count equal to 0 which mucks things up.

What changes are included in this PR?

Are there any user-facing changes?

@github-actions github-actions bot added the parquet Changes to the parquet crate label Sep 5, 2022
@thinkharderdev
Copy link
Contributor Author

@tustvold FYI. This should fix the flaky test.

@@ -1015,7 +1014,7 @@ mod tests {
let mut selectors = vec![];

while total_rows < 7300 {
let row_count: usize = rand.gen_range(0..100);
let row_count: usize = rand.gen_range(1..100);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So RowSelector.row_count cannot be 0?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It can if you manually construct one as we do in this test but in practice it would be non-sensical (and you wouldn't ever get one if you built a RowSelection from ranges or BooleanArrays). So depending on your perspective we could consider this a bug in the ParquetRecordBatchReader (probably, not sure where the actual issue comes up) but I think if we did the solution would be to just disallow row counts of 0 explicitly.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps you could file a ticket describing the issue, I agree it isn't urgent but it should probably be looked into eventually (as it might unveil other issues).

@tustvold tustvold merged commit a37c038 into apache:master Sep 6, 2022
@ursabot
Copy link

ursabot commented Sep 6, 2022

Benchmark runs are scheduled for baseline = 31aaef2 and contender = a37c038. a37c038 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on ec2-t3-xlarge-us-east-2] ec2-t3-xlarge-us-east-2
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on test-mac-arm] test-mac-arm
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on ursa-i9-9960x] ursa-i9-9960x
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on ursa-thinkcentre-m75q] ursa-thinkcentre-m75q
Buildkite builds:
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
parquet Changes to the parquet crate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants