[
https://issues.apache.org/jira/browse/BEAM-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320805#comment-16320805
]
Kenneth Knowles commented on BEAM-3397:
---------------------------------------
It is hitting the arg list size limit because the maven config includes all the
deps of all the runners at the same time. So we can just bump the limit in
Dataflow (filed internal bug) to buy time. I don't think we should bother
fixing the maven config because gradle already has addressed the issue.
> beam_PreCommit_Java_MavenInstall failing on Dataflow integration test because
> of too long commandline
> -----------------------------------------------------------------------------------------------------
>
> Key: BEAM-3397
> URL: https://issues.apache.org/jira/browse/BEAM-3397
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow, testing
> Reporter: Luke Cwik
> Priority: Blocker
> Fix For: 2.3.0
>
>
> The Dataflow worker fails to launch the process because the command line is
> too long. The worker logs are riddled with a very long command line followed
> by this error message:
> `java failed with fork/exec /usr/local/bin/java: argument list too long`
> Example failures from run from master @
> 49981f15009de434af9c09c3c9f50003c7417b88
> https://builds.apache.org/view/A-D/view/Beam/job/beam_PreCommit_Java_MavenInstall/16428/
> Job ids (project: apache-beam-testing):
> 2017-12-28_01_32_55-16084854344397840285
> 2017-12-28_01_32_55-213040034028880428
> 2017-12-28_01_32_55-16742595557951289122
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
