[ https://issues.apache.org/jira/browse/SPARK-24825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547133#comment-16547133 ]
Stavros Kontopoulos edited comment on SPARK-24825 at 7/17/18 9:37 PM: ---------------------------------------------------------------------- You could remove .m2, downloads should be fast. :) I am hacking too :P But I suspect also timestamp of published metadata is messed up. Can we ping people who own the process? [~srowen]? was (Author: skonto): You could remove .m2, downloads should be fast. :) I am hacking too :P But i suspect also timestamp of published metadata are messed up. Can we ping people who own the process? [~srowen]? > [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: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org