Added the port erasure to SparkFunSuite's cleanup.

[tdanford]

Fixes ISSUE #103

We've been getting intermittent errors, with respect to Spark being unable to bind to a port,
in the context of repeated unit tests. This apparently is a known problem, see the thread here:
http://blog.quantifind.com/posts/spark-unit-test/
and the follow-up from Matei here:
https://groups.google.com/forum/#!topic/spark-users/MeVzgoJXm8I

The upshot is that we need to clearProperty('spark.driver.port') when we shut down our sparkContext
after a sparkTest.

[AmplabJenkins]

All automated tests passed.
Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/ADAM-prb/114/

[tdanford]

Hold off on merging this for now ... Carl and I are still tracking something down.

[fnothaft]

Nit: there should be a space between entries.

[fnothaft]

Thanks @tdanford and @carlyeks . I believe you are still doing some further analysis, so I will wait for your all-clear before merging this.

[tdanford]

Yeah, we're still looking-- this isn't quite fixing all our problems yet. We're going to have to run scalatest by hand, since we can't get it to stop truncating our stack traces through maven :-/

On Thu, Feb 13, 2014 at 3:58 PM, Frank Austin Nothaft
notifications@github.com wrote:

Thanks @tdanford and @carlyeks . I believe you are still doing some further analysis, so I will wait for your all-clear before merging this.

Reply to this email directly or view it on GitHub:
#104 (comment)

[AmplabJenkins]

All automated tests passed.
Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/ADAM-prb/120/

[tdanford]

Okay, once the Jenkins build succeeds, this request should be ready (again) for review.

[AmplabJenkins]

All automated tests passed.
Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/ADAM-prb/121/

[fnothaft]

Thanks @tdanford and @carlyeks !

[tdanford]

Thanks Frank!