[
https://issues.apache.org/jira/browse/ARROW-16943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561177#comment-17561177
]
Kouhei Sutou commented on ARROW-16943:
--------------------------------------
[~raulcd] It seems that java-jars nightly job uses self-hosted runner with
{{runs-on: macos-latest}} since 2022-06-23. Do you know why it is occurred?
* 2022-06-23 job log:
https://github.com/ursacomputing/crossbow/runs/7027946353?check_suite_focus=true
* 2022-06-23 workflow file:
https://github.com/ursacomputing/crossbow/actions/runs/2547855667/workflow#L123
> [Java][Packaging] Nigthly build is generating excessive jars
> ------------------------------------------------------------
>
> Key: ARROW-16943
> URL: https://issues.apache.org/jira/browse/ARROW-16943
> Project: Apache Arrow
> Issue Type: Bug
> Components: Java, Packaging
> Reporter: Anthony Louis Gotlib Ferreira
> Assignee: Anthony Louis Gotlib Ferreira
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Since June 24 the nightly build is generating multiple jars for the same
> module.
> In that example:
> [https://github.com/ursacomputing/crossbow/releases/tag/nightly-packaging-2022-06-24-0-github-java-jars]
> you can find three different jars for the arrow-gandiva.
> I looked at the scripts for java build, the jinja macros that upload the
> artifacts, and the YAML file that defines the job for java jars, and all
> files were not changed recently. Maybe it is a problem inside the environment
> where the job is running.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
