GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/2221
SPARK-3330 [BUILD] Successive test runs with different profiles fail
SparkSubmitSuite
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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/srowen/spark SPARK-3330
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/2221.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2221
----
commit 6d189ea166656135ad5803c59a4ddfc973f79c60
Author: Sean Owen <[email protected]>
Date: 2014-08-31T17:23:18Z
Clean assembly/target from parent clean target since assembly is not a
submodule. Otherwise multiple assemblies can accumulate during, say, Jenkins
tests and fail unit tests
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
