You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2014/09/03 00:06:20 UTC
[jira] [Resolved] (SPARK-3330) Successive test runs with different
profiles fail SparkSubmitSuite
[ https://issues.apache.org/jira/browse/SPARK-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen resolved SPARK-3330.
------------------------------
Resolution: Won't Fix
It will be more suitable to change jenkins to run "mvn clean && mvn ... package" to address this, if anything. It's not yet clear this is the cause of the failure in the same test in Jenkins though.
> Successive test runs with different profiles fail SparkSubmitSuite
> ------------------------------------------------------------------
>
> Key: SPARK-3330
> URL: https://issues.apache.org/jira/browse/SPARK-3330
> Project: Spark
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.0.2
> Reporter: Sean Owen
>
> Maven-based Jenkins builds have been failing for a while:
> https://amplab.cs.berkeley.edu/jenkins/view/Spark/job/Spark-Master-Maven-with-YARN/480/HADOOP_PROFILE=hadoop-2.4,label=centos/console
> One common cause is that on the second and subsequent runs of "mvn clean test", at least two assembly JARs will exist in assembly/target. Because assembly is not a submodule of parent, "mvn clean" is not invoked for assembly. The presence of two assembly jars causes spark-submit to fail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org