Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5096#issuecomment-91040738
i'll up it to 180, just so we have some headroom.
On Wed, Apr 8, 2015 at 2:21 PM, Shivaram Venkataraman <
[email protected]> wrote:
> @brennonyork <https://github.com/brennonyork> The overall Jenkins build
> runner has a timeout of 130 minutes right now (cc @shaneknapp
> <https://github.com/shaneknapp>). So all the RAT tests, Mima checks,
> style checks, new dependencies plus all the unit tests have to run within
> 130 minutes and this PR seems to be failing that.
>
> @shaneknapp <https://github.com/shaneknapp> can we increase the 130 min
> timeout to say 140 minutes ?
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/5096#issuecomment-91040259>.
>
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
