Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/20697
> 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?
Every PR build runs that script. It would avoid having special jobs just
for kubernetes testing (which, frankly, as someone who is not working on k8s
stuff 99.9% of the time, is super confusing). If not all hosts currently can
run them, then it's ok to postpone this. But I still think all PR testing
should be, eventually, tied to that script.
For example, release managers generally use that script for testing, and
doing so would allow them to easily include kubernetes in their testing without
having to jump through hoops.
If you're worried about your own testing, you can follow the python / R
approach and have a separate "run-tests" script, and call that one from the
main run-tests script.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
