Adding support for before, after clauses to SparkFunSuite. #25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I had a problem, with another branch, where I couldn't access the SparkContext inside a before{}
or after{} block in a SparkFunSuite. This tries to fix that problem -- and refactors the creation
and destruction of the sparkcontext into separate methods for reuse.
I'm not sure if there's a problem though, with multi-threaded execution of tests? This seems fragile,
somehow, and could use some comments/review.
|
Merged build triggered. |
|
Merged build started. |
|
Merged build finished. |
|
All automated tests passed. |
massie
added a commit
that referenced
this pull request
Dec 12, 2013
Adding support for before, after clauses to SparkFunSuite.
|
Thanks, Timothy! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had a problem, with another branch, where I couldn't access the SparkContext inside a before{}
or after{} block in a SparkFunSuite. This tries to fix that problem -- and refactors the creation
and destruction of the sparkcontext into separate methods for reuse.
I'm not sure if there's a problem though, with multi-threaded execution of tests? This seems fragile,
somehow, and could use some comments/review.