Github user shaneknapp commented on the issue:
https://github.com/apache/spark/pull/20697
just wanted to chime in here:
i went to databricks a couple of weeks back and have confirmation that
after the spark summit, that i will officially have build system support
from them! this took a lot of time for me to wrangle, but it's finally
happened. :)
the biggest win for us here is that getting spark builds ported to ubuntu
in the next couple of months. this means that we'll have minikube
installed on all of the workers.
so... yeah. i'll have a much, much, much better idea of when we'll be
getting more ubuntu workers on-line as well as ubuntu-friendly (or fully
containerized) spark tests within the next 3-4 weeks.
shane
On Fri, May 25, 2018 at 2:16 PM, Sean Suchter <[email protected]>
wrote:
> Hm, that wasn't the answer I expected to hear. It leads me to another
> question:
>
> If we don't have developers using this script directly, what's the value
> of trying to incorporate the running of the Kubernetes integration tests
> into this program? Because of the AMPLab setup, we're going to have to
have
> special Jenkins jobs dedicated to the running of the K8s integration
tests.
> This is because not all hosts can run these integration tests, so
therefore
> we have special jobs that are tied to the specific hosts that have the
> right setup to run the minikube VMs. So it's just going to be those jobs
> that call dev/run-tests.py with the special non-default argument to run
> these tests. Those jenkins jobs could just as easily run a different
script.
>
> An alternative way to take my argument is that we should delay the
> integration into run-tests.py until after *all* of the AMPLab hosts can
> run these tests. Since that's not today, it wouldn't need to be in this
> initial PR, and could have its own PR.
>
> Thoughts? Thanks, Sean
>
> â
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/spark/pull/20697#issuecomment-392189209>, or
mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/ABiDrFJdW_7DLsOILqAJ1ENZyZml4tc4ks5t2HSxgaJpZM4SXRkC>
> .
>
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
