Github user ryan-williams commented on the pull request:
https://github.com/apache/spark/pull/2848#issuecomment-67253690
Thanks a lot for the build-process brain-dump, @JoshRosen; some of that is
way better than processes I've wasted a lot of time on. I'm interested in
getting all of these tips and tricks pushed to Spark docs, but even after all
of the emailing your response includes tricks I've not seen documented anywhere
(e.g. `SPARK_PREPEND_CLASSES`), so I'm leery of spending time trying to
document what I've learned for fear that I'm still not at the bottom of the
rabbit hole.
In any case, I was able to debug and (I believe) fix the test failure,
which was a result of having inadvertently changed a file "copy" to a "move",
so it's a good thing the test caught it.
This should be ready to re-test.
---
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
