dongjoon-hyun commented on pull request #29621: URL: https://github.com/apache/spark/pull/29621#issuecomment-718215661
This PR doesn't pass K8s IT since September. - https://github.com/apache/spark/pull/29621#issuecomment-685170312 - https://github.com/apache/spark/pull/29621#issuecomment-685235211 - https://github.com/apache/spark/pull/29621#issuecomment-718138054 - https://github.com/apache/spark/pull/29621#issuecomment-718196120 - https://github.com/apache/spark/pull/29621#issuecomment-718196579 The failures are on the following test cases. Recently, Jenkins K8s IT seems to be unstable. - Run SparkPi with no resources (Failed always, but known to be flaky) - Run SparkPi with a very long application name. (failed once in the above) - Run SparkR on simple dataframe.R example (Failed always, but known to be flaky So, I verified manually on my laptop. ``` ubernetesSuite: - Run SparkPi with no resources - Run SparkPi with a very long application name. - Use SparkLauncher.NO_RESOURCE - Run SparkPi with a master URL without a scheme. - Run SparkPi with an argument. - Run SparkPi with custom labels, annotations, and environment variables. - All pods have the same service account by default - Run extraJVMOptions check on driver - Run SparkRemoteFileTest using a remote data file - Run SparkPi with env and mount secrets. - Run PySpark on simple pi.py example - Run PySpark with Python2 to test a pyfiles example - Run PySpark with Python3 to test a pyfiles example - Run PySpark with memory customization - Run in client mode. - Start pod creation from template - PVs with local storage - Launcher client dependencies - Run SparkR on simple dataframe.R example Run completed in 10 minutes, 17 seconds. ``` For the K8s IT failure, I've been taking a look independently. - https://github.com/apache/spark/pull/30130 ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
