Github user squito commented on the pull request:
https://github.com/apache/spark/pull/4048#issuecomment-70008794
@pwendell To be honest I'd never had the patience to run all the tests
before on my laptop. But I just tried them both again: 237 seconds vs. 852
seconds (just for core), so these tests are down to ~25% of the total time. It
makes using `test-quick` a reality, while I have no end of complaints about
sbt, I really like `test-quick`.
@vanzin yeah there are also a bunch of tests in other projects, I know
there are a bunch in mllib as well. (I guess this is really a WIP at this
point, wanted to see if I folks like the idea before I do it in other projects.)
@srowen I wasn't familiar with `surefire` or `failsafe` from maven, but I
figured there was some other way to just support an integration test
separation. I am just more familiar with tagging tests, and I think it buys us
some more flexibility. I'll see if I can figure out how to setup a maven task
(or whatever its called) to only run the unit tests, but I know very little
about maven ...
---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
