Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/77#issuecomment-36686522
OK that works, to package and then test. In the canonical Maven lifecycle,
packaging comes after test, so test would not depend on packaging. In practice
this is at worst a
Github user srowen closed the pull request at:
https://github.com/apache/spark/pull/77
---
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 enable
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/77#issuecomment-36669615
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12997/
---
If your pr
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/77#issuecomment-36669614
Merged build finished.
---
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 t
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/77#issuecomment-36665859
In Maven, you can run tests that depend on packages/assemblies during
Maven's `integration-test` phase, which automatically runs after the Maven
`package` phase. I'm not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/77#issuecomment-36663340
Merged build triggered.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/77#issuecomment-36663341
Merged build started.
---
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 th
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/77#issuecomment-36659947
The standard maven build procedure should be to run `mvn -DskipTests
package` first (which builds the assembly) and then `mvn test`. The "Building
Spark with Maven" pa
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/77
SPARK-1181. 'mvn test' fails out of the box since sbt assembly does not
necessarily exist
The test suite requires that "sbt assembly" has been run in order for some
tests (like DriverSuite) to pass. T
