HeartSaVioR commented on pull request #29036: URL: https://github.com/apache/spark/pull/29036#issuecomment-655796622
Summary of the 5 builds: > 125347 (https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/125347/testReport/) All tests in CliSuite passed. > 125348 (https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/125348/testReport/) A bunch of tests in CliSuite failed, though looks like the build was super slow, bunch of other suites also failed as well. > 125350 (https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/125350/testReport/) Only one test in CliSuite failed, and it wasn't about timeout - `org.scalatest.exceptions.TestFailedException: spark-sql did not exit gracefully.`. I wonder we really have to fail the test for the case. > 125351 (https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/125351/testReport/) All tests in CliSuite passed. > 125353 (https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/125353/testReport/) Except the failures of `org.scalatest.exceptions.TestFailedException: spark-sql did not exit gracefully.`, only one test failed (path command), and boot timeout actually helped to run the query. Just because query execution timeout was short. Looks like this fix helps mitigating the flakiness. Let me update the patch to not fail the query for `spark-sql did not exit gracefully`, and give more time on `path command`. ---------------------------------------------------------------- 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]
