dongjoon-hyun opened a new pull request, #114:
URL: https://github.com/apache/spark-docker/pull/114

   ### What changes were proposed in this pull request?
   
   This PR is a followup of SPARK-56783 and aims to disable Apache Spark's 
`volcano` profile during K8S IT by patching the checked-out `pom.xml` with 
`sed` instead of relying on the `-P!volcano` sbt option.
   
   ### Why are the changes needed?
   
   The previously added `-P!volcano` is a Maven CLI deactivation syntax that 
sbt's `sbt-pom-reader` does not honor. In Apache Spark's 
`project/SparkBuild.scala`, the profile parser strips only the `-P` prefix and 
then feeds `!volcano` back as a profile name to activate, which is silently 
ignored. The `volcano` profile in 
`resource-managers/kubernetes/integration-tests/pom.xml` is 
`activeByDefault=true` since `v4.2.0-preview5`, so it remained active and 
caused `VolcanoSuite` to run and fail on the `minikube` cluster:
   
   ```
   [info] VolcanoSuite:
   [info] - SPARK-42190: Run SparkPi with local[*] *** FAILED *** (3 minutes, 3 
seconds)
   ```
   
   This change instead patches the checked-out `pom.xml` so the `volcano` 
profile is no longer `activeByDefault`, which works regardless of whether sbt 
or Maven is invoked. It is a no-op for Spark `<= 4.1.x` where `volcano` is not 
`activeByDefault`.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No. This is a CI-only change.
   
   ### How was this patch tested?
   
   Pass the CIs.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Opus 4.7 (1M context)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to