-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-19684] [DOCS] Remove developer info from docs. #17018
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This commit moves developer-specific information from the release- specific documentation in this repo to the developer tools page on the main Spark website. This commit relies on this PR on the Spark website: apache/spark-website#33.
|
Test build #73237 has finished for PR 17018 at commit
|
|
Test build #73356 has finished for PR 17018 at commit
|
|
Just to clarify what I meant is that there was a similar error fixed due to Hadoop / SQL issues by @HyukjinKwon in #16927 - I'll see if this happens again and file a issue if it does |
|
Hmm I think this specific one timed out, so it might not be worth investigating https://ci.appveyor.com/project/ApacheSoftwareFoundation/spark/build/824-master/messages |
|
Let me run a build in my account to double check and create a JIRA with cc'ing you if it is broken. |
|
Thanks for cc'ing me. |
|
Ah, this one seems timed out because it exceeds the 1 hour limitation of execution time in AppVeyor. It seems now R tests could take longer than an hour including the build rarely. This limit could be increased a bit by asking. My account has 1 and half hours (I asked AppVeyor team when I tried to run some Scala/Java tests). Let me maybe try to ask increasing it first if you all think it is fine. If it can be a problem with the increased time in the future, let me try to split the tests as I did for Scala/Java tests in my account e.g., https://ci.appveyor.com/project/spark-test/spark/build/632-20170219-windows-test |
|
Yeah asking them for 1.5hr seems like a good first step. We can also see what fraction of time it takes for build vs. tests. I guess we can't make builds faster without some effort, but we could look at making the tests faster or running a subset of them (for example the RDD tests in SparkR are probably not high priority as the API is private etc.) |
|
I see. Sure. Just as a side note, if you download the log, it prints the times. In this case, it was so close assuming from the last log :). |
|
I have a confirmation that it is increased to 90 mins now. |
|
Thanks - will keep an eye out to see if the time out errors are gone. |
This commit moves developer-specific information from the release- specific documentation in this repo to the developer tools page on the main Spark website. This commit relies on this PR on the Spark website: apache/spark-website#33. srowen Author: Kay Ousterhout <[email protected]> Closes apache#17018 from kayousterhout/SPARK-19684.
This commit moves developer-specific information from the release-
specific documentation in this repo to the developer tools page on
the main Spark website. This commit relies on this PR on the
Spark website: apache/spark-website#33.
@srowen