[
https://issues.apache.org/jira/browse/SPARK-24825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547225#comment-16547225
]
Stavros Kontopoulos edited comment on SPARK-24825 at 7/17/18 11:43 PM:
-----------------------------------------------------------------------
Yes [~srowen] is right, this seems to work:
dev-run-integration-tests.sh:
cd ../../../
./build/mvn -T 1C -Pscala-2.11 -Pkubernetes -pl
resource-managers/kubernetes/integration-tests -amd integration-test
$\{properties[@]}
was (Author: skonto):
Yes [~srowen] is right, this seems to work:
dev-run-integration-tests.sh
cd ../../../
./build/mvn -T 1C -Pscala-2.11 -Pkubernetes -pl
resource-managers/kubernetes/integration-tests -amd integration-test
$\{properties[@]}
> [K8S][TEST] Kubernetes integration tests don't trace the maven project
> dependency structure
> -------------------------------------------------------------------------------------------
>
> Key: SPARK-24825
> URL: https://issues.apache.org/jira/browse/SPARK-24825
> Project: Spark
> Issue Type: Bug
> Components: Kubernetes, Tests
> Affects Versions: 2.4.0
> Reporter: Matt Cheah
> Priority: Critical
>
> The Kubernetes integration tests will currently fail if maven installation is
> not performed first, because the integration test build believes it should be
> pulling the Spark parent artifact from maven central. However, this is
> incorrect because the integration test should be building the Spark parent
> pom as a dependency in the multi-module build, and the integration test
> should just use the dynamically built artifact. Or to put it another way, the
> integration test builds should never be pulling Spark dependencies from maven
> central.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
