Skip to content

SPARK-3404 [BUILD] SparkSubmitSuite fails with "spark-submit exits with code 1" #2328

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

srowen
Copy link
Member

@srowen srowen commented Sep 9, 2014

This fixes the SparkSubmitSuite failure by setting <spark.ui.port>0</spark.ui.port> in the Maven build, to match the SBT build. This avoids a port conflict which causes failures.

(This also updates the scalatest plugin off of a release candidate, to the identical final release.)

…avoid SparkSubmitSuite failure due to port conflict
@SparkQA
Copy link

SparkQA commented Sep 9, 2014

QA tests have started for PR 2328 at commit 512d782.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Sep 9, 2014

QA tests have finished for PR 2328 at commit 512d782.

  • This patch fails unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@rxin
Copy link
Contributor

rxin commented Sep 9, 2014

@JoshRosen

I guess this still doesn't fix the SBT test flakiness, but it should help with the Maven ones (at least bring them up to par with SBT).

@JoshRosen
Copy link
Contributor

If this gives us a green build under Maven, it should also fix SPARK-2232. Getting the Maven master builds up to par with SBT would be a good milestone.

It looks like the test failure here is due to a known issue that will be fixed in #2334.

@rxin
Copy link
Contributor

rxin commented Sep 9, 2014

Merging in master. Thanks.

@asfgit asfgit closed this in f0f1ba0 Sep 9, 2014
@srowen srowen deleted the SPARK-3404 branch September 15, 2014 14:33
@@ -888,7 +888,7 @@
<plugin>
<groupId>org.scalatest</groupId>
<artifactId>scalatest-maven-plugin</artifactId>
<version>1.0-RC2</version>
<version>1.0</version>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@srowen does this need to be back ported into 1.1 as well?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nah, this is not necessary to back-port.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants