Describe the bug
While verifying DataFusion 53.0.0, we found that the verify_release_candidate script was not working correctly, as it was hitting an assertion
To Reproduce
Specifically:
$ ./dev/release/verify-release-candidate.sh 53.0.0 2
...
joins::sort_merge_join::tests::test_should_emit_early_when_have_enough_data_to_emit
test result: FAILED. 1190 passed; 78 failed; 0 ignored; 0 measured; 0 filtered out; finished in 8.89s
error: test failed, to rerun pass `-p datafusion-physical-plan --lib`
+ cleanup
+ '[' no = yes ']'
+ echo 'Failed to verify release candidate. See /var/folders/1l/tg68jc6550gg8xqf1hr4mlwr0000gn/T/datafusion-53.0.0.XXXXX.d5aUZcsu7v for details.'
Failed to verify release candidate. See /var/folders/1l/tg68jc6550gg8xqf1hr4mlwr0000gn/T/datafusion-53.0.0.XXXXX.d5aUZcsu7v for details.
The failure is due to an overzealous assert in arrow-rs (see apache/arrow-rs#9506) that will be fixed in the next release
The reason this isn' triggered on CI is that sqllogictests are run with --profile=ci -- see
https://github.com/apache/datafusion/blob/11b9693952cd419b73dd03cc39f22c8b343bc05c/.github/workflows/rust.yml#L299-L298
Expected behavior
verification should pass
Additional context
No response
Describe the bug
While verifying DataFusion 53.0.0, we found that the
verify_release_candidatescript was not working correctly, as it was hitting an assertionTo Reproduce
Specifically:
$ ./dev/release/verify-release-candidate.sh 53.0.0 2 ... joins::sort_merge_join::tests::test_should_emit_early_when_have_enough_data_to_emit test result: FAILED. 1190 passed; 78 failed; 0 ignored; 0 measured; 0 filtered out; finished in 8.89s error: test failed, to rerun pass `-p datafusion-physical-plan --lib` + cleanup + '[' no = yes ']' + echo 'Failed to verify release candidate. See /var/folders/1l/tg68jc6550gg8xqf1hr4mlwr0000gn/T/datafusion-53.0.0.XXXXX.d5aUZcsu7v for details.' Failed to verify release candidate. See /var/folders/1l/tg68jc6550gg8xqf1hr4mlwr0000gn/T/datafusion-53.0.0.XXXXX.d5aUZcsu7v for details.The failure is due to an overzealous assert in arrow-rs (see apache/arrow-rs#9506) that will be fixed in the next release
The reason this isn' triggered on CI is that sqllogictests are run with
--profile=ci-- seehttps://github.com/apache/datafusion/blob/11b9693952cd419b73dd03cc39f22c8b343bc05c/.github/workflows/rust.yml#L299-L298
Expected behavior
verification should pass
Additional context
No response