The test failures look unrelated, and are a Jenkins error.

You should just make one PR for master; it will be back-ported as needed.

On Tue, Jan 27, 2015 at 1:58 PM, jacek-lewandowski <g...@git.apache.org> wrote:
> Github user jacek-lewandowski commented on the pull request:
>
>     https://github.com/apache/spark/pull/4220#issuecomment-71651118
>
>     What is going on with these tests??? I've created three PRs - for 1.1, 
> 1.2 and 1.3 and all of them failed in a very strange way.
>
>
> ---
> 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
>

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to