Github user vanzin commented on the issue:

    https://github.com/apache/spark/pull/20697
  
    > In terms of integration with the dev/run-tests.py, we at most want to 
make it optional.
    
    It's fine to make them optional; in fact that would be a requirement. The 
trick would be to run them automatically when there are interesting changes 
(e.g. changes in the k8s module), and do that as part of the normal PR build, 
instead of having a separate job that runs k8s integration tests.
    
    I'm not sure what's the current distribution of hosts (Shane can comment on 
that). but if they all can run k8s integration tests, then I think that would 
be a better solution than having two separate jobs.


---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to