Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-185328477
the last failed build was due to a timeout reaching github... this is
something that's been ongoing now for a couple of years and it's definitely
on their end. we're not hitting any rate limits or things like that. let
me retrigger and see what happens.
On Wed, Feb 17, 2016 at 10:01 AM, Luciano Resende <notificati...@github.com>
wrote:
> @JoshRosen <https://github.com/JoshRosen> @shaneknapp
> <https://github.com/shaneknapp> I believe this is ready, but Jenkins
> seems to be having timeout issues probably when connecting to the db2
> docker image. Is there a way for any of you guys with access to the slave
> to see if there is any info that might give some hints on what's going on
?
> I have tried to increase the timout on the test without much success.
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/9893#issuecomment-185326608>.
>
---
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
