Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
Description
Some tests - in particular tests that have to spawn child processes - currently rely on the generated Spark assembly to run properly.
This is sub-optimal for a few reasons:
- Users have to use an unnatural "package everything first, then run tests" approach
- Sometimes tests are run using old code because the user forgot to rebuild the assembly
The latter is particularly annoying in YarnClusterSuite. If you modify some code outside of the yarn/ module, you have to rebuild the whole assembly before that test picks it up.
We should make all tests run without the need to have an assembly around, making sure that they always pick up the latest code compiled by the user.
Attachments
Issue Links
- links to