Yeah, that's maybe the issue here. This is a source release, not a git checkout, and it still needs to work in this context.
I just added -Pkubernetes to my build and didn't do anything else. I think the ideal is that a "mvn -P... -P... install" to work from a source release; that's a good expectation and consistent with docs. Maybe these tests simply don't need to run with the normal suite of tests, and can be considered tests run manually by developers running these scripts? Basically, KubernetesSuite shouldn't run in a normal mvn install? I don't think this has to block the release even if so, just trying to get to the bottom of it. On Tue, Oct 23, 2018 at 10:58 AM Stavros Kontopoulos < stavros.kontopou...@lightbend.com> wrote: > Ok I missed the error one line above, before the distro error there is > another one: > > fatal: not a git repository (or any of the parent directories): .git > > > So that seems to come from here > <https://github.com/apache/spark/blob/master/resource-managers/kubernetes/integration-tests/scripts/setup-integration-test-env.sh#L19>. > It seems that the test root is not set up correctly. It should be the top > git dir from which you built Spark. > > Now regarding the distro thing. dev-run-integration-tests.sh should run > from within the cloned project after the distro is built. The distro is > required > <https://github.com/apache/spark/blob/master/resource-managers/kubernetes/integration-tests/scripts/setup-integration-test-env.sh#L61> > , it should fail otherwise. > > Integration tests run the setup-integration-test-env.sh script. > dev-run-integration-tests.sh > calls mvn > <https://github.com/apache/spark/blob/master/resource-managers/kubernetes/integration-tests/dev/dev-run-integration-tests.sh#L106> > which > in turn executes that setup script > <https://github.com/apache/spark/blob/master/resource-managers/kubernetes/integration-tests/pom.xml#L80> > . > > How do you run the tests? > >
