Thanks for opening a pull request!

If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose

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

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

GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

or

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

In the case of PARQUET issues on JIRA the title also supports:

PARQUET-${JIRA_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

See also:

• Other pull requests
• Contribution Guidelines - Contributing Overview

@github-actions crossbow submit java

@davisusanibar Could you take a look at this?

@github-actions crossbow submit -g java

Revision: 1b19015

Submitted crossbow builds: ursacomputing/crossbow @ actions-9091e1770d

Task	Status
java-jars
verify-rc-source-java-linux-almalinux-8-amd64
verify-rc-source-java-linux-conda-latest-amd64
verify-rc-source-java-linux-ubuntu-20.04-amd64
verify-rc-source-java-linux-ubuntu-22.04-amd64
verify-rc-source-java-macos-amd64

@vibhatha You don't need to submit new jobs for re-run. You can just use the "Re-run jobs" button in the GitHub Actions page: https://github.com/ursacomputing/crossbow/actions/runs/8340911888/job/22827112337

@kou I cannot see a re-run button.

@raulcd Could you check whether @vibhatha has a right to re-run jobs or not?

@kou btw seems like CIs are passing.

@davisusanibar what do you think about this comment: #40568 (comment)
Am I missing something here?

@raulcd Could you check whether @vibhatha has a right to re-run jobs or not?

He is not a member of the ursacomputing GitHub organization at the moment. He has the collaborator role on the arrow project which allows to assign issues and trigger crossbow jobs via GitHub comments but cannot re-run jobs on crossbow as far as I understand.

@davisusanibar it's because @indigophox reverted it (by accident?) in 2e2bd8b. Sorry, I didn't notice that change at the time. So we can merge this and update the testing submodule properly.

After merging your PR, Conbench analyzed the 0 benchmarking runs that have been run so far on merge-commit 07e8aa2.

None of the specified runs were found on the Conbench server.

The full Conbench report has more details.