[
https://issues.apache.org/jira/browse/BEAM-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15488356#comment-15488356
]
Eugene Kirpichov commented on BEAM-630:
---------------------------------------
Some investigation:
- The issue can be narrowed down to "-DforkCount=0" - "mvn clean test
-DforkCount=0" fails in this way, but a simple "mvn clean test" passes.
- The class files generated with and without this option are identical.
- On my machine, system properties with and without this option are nearly
identical: the differing properties are classworlds.conf, java.class.path,
magen.home, maven.multiModuleProjectDirectory, securerandom.source,
sun.java.command. The JVM version et al. are the same. I don't see how any of
these properties could affect whether or not the class verifies.
> DataflowRunnableOnService test suite is broken
> ----------------------------------------------
>
> Key: BEAM-630
> URL: https://issues.apache.org/jira/browse/BEAM-630
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Affects Versions: Not applicable
> Reporter: Daniel Halperin
> Assignee: Eugene Kirpichov
>
> Looks like it's related to problems with the new DoFnSignatures/Invoker:
> https://builds.apache.org/job/beam_PostCommit_RunnableOnService_GoogleCloudDataflow/1134/#showFailuresLink
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
