[GitHub] spark pull request: Enabled incremental build that comes with sbt ...
Github user ScrapCodes commented on the pull request: https://github.com/apache/spark/pull/525#issuecomment-42404934 @markhamstra I was curious if you are convinced ? --- 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. ---
[GitHub] spark pull request: Enabled incremental build that comes with sbt ...
Github user asfgit closed the pull request at: https://github.com/apache/spark/pull/525 --- 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. ---
[GitHub] spark pull request: Enabled incremental build that comes with sbt ...
Github user pwendell commented on the pull request: https://github.com/apache/spark/pull/525#issuecomment-42761542 Okay I think since there doesn't seem to be anything _bad_ about adding this we can try it out. This is only a developer-facing change and shouldn't affect users at all. We can turn it off if there are issues. --- 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. ---
[GitHub] spark pull request: Enabled incremental build that comes with sbt ...
Github user ScrapCodes commented on the pull request: https://github.com/apache/spark/pull/525#issuecomment-41789534 Yes I did, in order to try that out. put sbt in continuous compilation. like `sbt ~compile` after that make a minor change to SparkContext such that it does not affect any other file. For example make a private field public. Try doing this with this option and without it, I am sure you will see for your self the difference in the times of compilations. --- 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. ---
[GitHub] spark pull request: Enabled incremental build that comes with sbt ...
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/525#issuecomment-41250490 Merged build triggered. --- 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. ---
[GitHub] spark pull request: Enabled incremental build that comes with sbt ...
GitHub user ScrapCodes opened a pull request: https://github.com/apache/spark/pull/525 Enabled incremental build that comes with sbt 0.13.2 More info at. https://github.com/sbt/sbt/issues/1010 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ScrapCodes/spark-1 sbt-inc-opt Alternatively you can review and apply these changes as the patch at: https://github.com/apache/spark/pull/525.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #525 commit ba8fa42cf599c738b2a0c1941a0d7f40889e8d03 Author: Prashant Sharma prashan...@imaginea.com Date: 2014-04-24T07:14:09Z Enabled incremental build that comes with sbt 0.13.2 --- 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. ---
[GitHub] spark pull request: Enabled incremental build that comes with sbt ...
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/525#issuecomment-41253087 Merged build finished. All automated tests passed. --- 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. ---
[GitHub] spark pull request: Enabled incremental build that comes with sbt ...
Github user markhamstra commented on the pull request: https://github.com/apache/spark/pull/525#issuecomment-41299187 Did you actually find any benefit to adding this option? Previously, I tried the same thing that you are doing in this PR (just a few lines earlier in the file, right after the javacOptions), ran several duplicate incremental builds from various starting states, differing in whether withNameHashing was turned on or not, and I never found any clear advantage in terms of compile time in that small sample. --- 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. ---
