Yikun commented on pull request #35557: URL: https://github.com/apache/spark/pull/35557#issuecomment-1043110400
Integrations test passed: ``` [info] KubernetesSuite: [info] - Run SparkPi with no resources (12 seconds, 129 milliseconds) [info] - Run SparkPi with no resources & statefulset allocation (11 seconds, 672 milliseconds) [info] - Run SparkPi with a very long application name. (10 seconds, 643 milliseconds) [info] - Use SparkLauncher.NO_RESOURCE (10 seconds, 588 milliseconds) [info] - Run SparkPi with a master URL without a scheme. (10 seconds, 554 milliseconds) [info] - Run SparkPi with an argument. (11 seconds, 571 milliseconds) [info] - Run SparkPi with custom labels, annotations, and environment variables. (10 seconds, 611 milliseconds) [info] - All pods have the same service account by default (10 seconds, 532 milliseconds) [info] - Run extraJVMOptions check on driver (5 seconds, 528 milliseconds) [info] - Run SparkRemoteFileTest using a remote data file (11 seconds, 728 milliseconds) [info] - Verify logging configuration is picked from the provided SPARK_CONF_DIR/log4j2.properties (18 seconds, 19 milliseconds) [info] - Run SparkPi with env and mount secrets. (19 seconds, 567 milliseconds) [info] - Run PySpark on simple pi.py example (12 seconds, 546 milliseconds) [info] - Run PySpark to test a pyfiles example (14 seconds, 668 milliseconds) [info] - Run PySpark with memory customization (11 seconds, 532 milliseconds) [info] - Run in client mode. (9 seconds, 195 milliseconds) [info] - Start pod creation from template (11 seconds, 609 milliseconds) [info] - Test basic decommissioning (45 seconds, 983 milliseconds) [info] - Test basic decommissioning with shuffle cleanup (46 seconds, 179 milliseconds) [info] - Test decommissioning with dynamic allocation & shuffle cleanups (2 minutes, 45 seconds) [info] - Test decommissioning timeouts (45 seconds, 264 milliseconds) [info] - SPARK-37576: Rolling decommissioning (1 minute, 8 seconds) [info] VolcanoSuite: [info] - Run SparkPi with no resources (11 seconds, 556 milliseconds) [info] - Run SparkPi with no resources & statefulset allocation (12 seconds, 690 milliseconds) [info] - Run SparkPi with a very long application name. (12 seconds, 538 milliseconds) [info] - Use SparkLauncher.NO_RESOURCE (11 seconds, 527 milliseconds) [info] - Run SparkPi with a master URL without a scheme. (11 seconds, 551 milliseconds) [info] - Run SparkPi with an argument. (12 seconds, 497 milliseconds) [info] - Run SparkPi with custom labels, annotations, and environment variables. (11 seconds, 551 milliseconds) [info] - All pods have the same service account by default (11 seconds, 532 milliseconds) [info] - Run extraJVMOptions check on driver (6 seconds, 552 milliseconds) [info] - Run SparkRemoteFileTest using a remote data file (13 seconds, 546 milliseconds) [info] - Verify logging configuration is picked from the provided SPARK_CONF_DIR/log4j2.properties (20 seconds, 99 milliseconds) [info] - Run SparkPi with env and mount secrets. (20 seconds, 245 milliseconds) [info] - Run PySpark on simple pi.py example (13 seconds, 631 milliseconds) [info] - Run PySpark to test a pyfiles example (16 seconds, 633 milliseconds) [info] - Run PySpark with memory customization (12 seconds, 558 milliseconds) [info] - Run in client mode. (9 seconds, 119 milliseconds) [info] - Start pod creation from template (11 seconds, 624 milliseconds) [info] - Test basic decommissioning (47 seconds, 931 milliseconds) [info] - Test basic decommissioning with shuffle cleanup (46 seconds, 962 milliseconds) [info] - Test decommissioning with dynamic allocation & shuffle cleanups (2 minutes, 46 seconds) [info] - Test decommissioning timeouts (46 seconds, 419 milliseconds) [info] - SPARK-37576: Rolling decommissioning (1 minute, 8 seconds) [info] - Run SparkPi with volcano scheduler (11 seconds, 567 milliseconds) ``` -- 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]
