Uh oh!
There was an error while loading. Please reload this page.
[SPARK-3431] [WIP] Parallelize Scala/Java test execution - #3564
Conversation
SparkQA
commented
Dec 3, 2014
Test build #24061 has finished for PR 3564 at commit
|
SparkQA
commented
Dec 3, 2014
Test build #24062 has finished for PR 3564 at commit
|
SparkQA
commented
Dec 3, 2014
Test build #24063 has finished for PR 3564 at commit
|
SparkQA
commented
Dec 3, 2014
Test build #24066 timed out for PR 3564 at commit |
SparkQA
commented
Dec 3, 2014
Test build #24078 timed out for PR 3564 at commit |
SparkQA
commented
Dec 4, 2014
Test build #24145 has finished for PR 3564 at commit
|
SparkQA
commented
Dec 4, 2014
Test build #24146 has finished for PR 3564 at commit
|
SparkQA
commented
Dec 4, 2014
Test build #24147 has finished for PR 3564 at commit
|
nchammas
commented
Dec 6, 2014
Jenkins, retest this please. |
SparkQA
commented
Dec 6, 2014
Test build #24203 has finished for PR 3564 at commit
|
nchammas
commented
Dec 6, 2014
Hmm, this error from the latest test is interesting: When I comment out the line grouping tests everything runs fine. Are the forked JVMs somehow not picking up paths or whatnot correctly? |
SparkQA
commented
Dec 10, 2014
Test build #24271 has finished for PR 3564 at commit
|
SparkQA
commented
Dec 10, 2014
Test build #24289 has finished for PR 3564 at commit
|
nchammas
commented
Dec 10, 2014
Jenkins, retest this please. |
SparkQA
commented
Dec 10, 2014
Test build #24300 timed out for PR 3564 at commit |
JoshRosen
commented
Dec 12, 2014
I tried running You also see this in Jenkins. This was the sort of output-interleaving problem that I mentioned on the JIRA. I wish that there was a way to work around this, since this can make it really hard to debug failures. |
JoshRosen
commented
Dec 12, 2014
Actually, maybe the interleaving isn't a big deal as long as we can rely on the test report XML to be properly displayed in Jenkins. |
nchammas
commented
Dec 12, 2014
Yeah, I'm ignoring the problem of interleaved output for now since I'm hitting two more critical problems first: 1) the tests aren't running successfully, or 2) the tests aren't running faster than before. That said, I'm slowing building a better mental model of how sbt works and how it can be configured. Unfortunately, there aren't many examples out there of how to do this stuff, so I often end up trawling through posts like this one and this one to see how others have parallelized their tests. |
SparkQA
commented
Dec 12, 2014
Test build #24395 has finished for PR 3564 at commit
|
SparkQA
commented
Dec 12, 2014
Test build #24398 has finished for PR 3564 at commit
|
nchammas
commented
Dec 12, 2014
Jenkins, retest this please. |
SparkQA
commented
Dec 12, 2014
Test build #24400 has finished for PR 3564 at commit
|
nchammas
commented
Dec 12, 2014
Jenkins, retest this please. |
SparkQA
commented
Dec 12, 2014
Test build #24401 has finished for PR 3564 at commit
|
SparkQA
commented
Dec 12, 2014
Test build #24402 has finished for PR 3564 at commit
|
nchammas
commented
Dec 12, 2014
Jenkins, retest this please. |
SparkQA
commented
Dec 12, 2014
Test build #24404 has finished for PR 3564 at commit
|
nchammas
commented
Dec 21, 2014
Hmm, taking a second look at how the Python tests are invoked, I wonder if we can use |
nchammas
commented
Dec 22, 2014
By the way, I opened a question on Stack Overflow about some kind of "show execution plan" feature in sbt. It would make understanding what sbt is doing easier as we refine the build configuration. |
SparkQA
commented
Dec 29, 2014
Test build #24852 has finished for PR 3564 at commit
|
JoshRosen
commented
Jan 6, 2015
Jenkins, retest this please. |
SparkQA
commented
Jan 6, 2015
Test build #25115 has finished for PR 3564 at commit
|
JoshRosen
commented
Jan 6, 2015
We've been slowly making progress on the streaming test refactoring and it looks like we're down to only three failing tests on this branch: I should be able to address the |
nchammas
commented
Jan 7, 2015
Sounds good. Thanks for following up; I haven't had a chance to look over this PR in a while. (Btw, I rebased for kicks. You can disregard the coming test run.) |
SparkQA
commented
Jan 7, 2015
Test build #25136 has finished for PR 3564 at commit
|
nchammas
commented
Jan 17, 2015
Jenkins, retest this please. |
SparkQA
commented
Jan 17, 2015
Test build #25706 has finished for PR 3564 at commit
|
nchammas
commented
Jan 21, 2015
Jenkins, retest this please. |
SparkQA
commented
Jan 21, 2015
Test build #25870 has finished for PR 3564 at commit
|
nchammas
commented
Jan 21, 2015
Not sure what to make of this @JoshRosen, but there are several more test failures in the most recent run than the 3 we thought we were down to. For example, why would this DriverSuite test fail? |
JoshRosen
commented
Jan 23, 2015
Jenkins, retest this please. |
SparkQA
commented
Jan 23, 2015
Test build #26005 has finished for PR 3564 at commit
|
SparkQA
commented
Jan 30, 2015
Test build #26430 has finished for PR 3564 at commit
|
nchammas
commented
Feb 8, 2015
Jenkinmensch, retest this please. |
SparkQA
commented
Feb 8, 2015
Test build #27031 timed out for PR 3564 at commit |
SparkQA
commented
Feb 25, 2015
Test build #27961 has finished for PR 3564 at commit
|
pwendell
commented
Jun 4, 2015
I'd like to close this issue for now pending further development. |
This is currently a work in progress to experiment with various options for parallelizing our Scala/Java tests using sbt.