ARROW-17385: [Integration] Re-enable Rust integration case

[lidavidm]

Follow up for ARROW-10961 (apache/arrow-rs#140).

Closes apache/arrow-rs#140

[github-actions]

Thanks for opening a pull request!

If this is not a minor PR. Could you open an issue for this pull request on JIRA? https://issues.apache.org/jira/browse/ARROW

Opening JIRAs ahead of time contributes to the Openness of the Apache Arrow project.

Then could you also rename pull request title in the following format?

ARROW-${JIRA_ID}: [${COMPONENT}] ${SUMMARY}

or

MINOR: [${COMPONENT}] ${SUMMARY}

See also:

• Other pull requests
• Contribution Guidelines - How to contribute patches

[github-actions]

https://issues.apache.org/jira/browse/ARROW-17385

[alamb]

Thanks @lidavidm -- I looked at the integration run https://github.com/apache/arrow/runs/7785878022?check_suite_focus=true and it definitely passes (though I didn't see anything explicitly in the logs about having run the scenario!)

[alamb]

Is there any reason to hold off merging this PR @lidavidm ?

I ask because of the somewhat scary sounding commit message DO NOT MERGE: [Integration] Re-enable Rust integration case 😅

[lidavidm]

Thanks @lidavidm -- I looked at the integration run https://github.com/apache/arrow/runs/7785878022?check_suite_focus=true and it definitely passes (though I didn't see anything explicitly in the logs about having run the scenario!)

Look for "C++ serving, Rust requesting" then scroll down to see "Testing file middleware" - on master it says -- Skipping test because consumer Rust does not support but it runs the test here

I ask because of the somewhat scary sounding commit message DO NOT MERGE: [Integration] Re-enable Rust integration case sweat_smile

Should be good, I just put that initially in case it did fail 😅

[alamb]

==========================================================
Testing file middleware

🚀 thanks @lidavidm and @carols10cents !

[lidavidm]

…huh, the new merge script uses the original commit and NOT the PR title like I would have expected.

[nealrichardson]

…huh, the new merge script uses the original commit and NOT the PR title like I would have expected.

If there's only one commit in the PR, the GitHub PR merge API will use the commit message and not the PR title (by default).

[lidavidm]

That's a little unfortunate :( I'll have to be more careful about commit messages

[nealrichardson]

We can probably fix this going forward in the merge script, though this specific commit message should get amended.

[lidavidm]

Hmm, is this worth force-pushing? I guess it hasn't been very long

[lidavidm]

Or we can revert and push again

[lidavidm]

Going off of https://lists.apache.org/thread/k7g8x0cwtcvn4rcj5tynzdlvhl5poy6f

[ursabot]

Benchmark runs are scheduled for baseline = b7c94e2 and contender = e2efc87. e2efc87 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Finished ⬇️0.0% ⬆️0.0%] ec2-t3-xlarge-us-east-2
[Failed ⬇️0.34% ⬆️0.0%] test-mac-arm
[Failed ⬇️0.55% ⬆️0.0%] ursa-i9-9960x
[Finished ⬇️0.11% ⬆️0.04%] ursa-thinkcentre-m75q
Buildkite builds:
[Finished] e2efc87f ec2-t3-xlarge-us-east-2
[Failed] e2efc87f test-mac-arm
[Failed] e2efc87f ursa-i9-9960x
[Finished] e2efc87f ursa-thinkcentre-m75q
[Finished] b7c94e2f ec2-t3-xlarge-us-east-2
[Failed] b7c94e2f test-mac-arm
[Failed] b7c94e2f ursa-i9-9960x
[Finished] b7c94e2f ursa-thinkcentre-m75q
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

[ursabot]

['Python', 'R'] benchmarks have high level of regressions.
test-mac-arm
ursa-i9-9960x

[alamb]

I am sorry @lidavidm -- I think I got too excited about this improvement and just hit the Enticing green button. I should have reviewed the dev process again. 😞

Thanks for cleaning up my mess

[lidavidm]

Ah, whoops! Well from Zulip apparently there's a setting we can ask Infra to toggle to also make that work, fortunately

[alamb]

I double checked and it seems like master has the change reverted (but not yet re-changed) https://github.com/apache/arrow/blob/master/dev/archery/archery/integration/runner.py#L433

Would it be helpful for me to to prepare a new PR with the change (revert the revert?)

[lidavidm]

I put one up here already: #13858

Just haven't run the merge script yet

[lidavidm]

And now it should be all good

[alamb]

Thanks again @lidavidm and sorry about that