venkata91 commented on pull request #28287: URL: https://github.com/apache/spark/pull/28287#issuecomment-657860016
> **[Test build #125783 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/125783/testReport)** for PR 28287 at commit [`b4c27fb`](https://github.com/apache/spark/commit/b4c27fb2539d10356bb4208e0509f7a32a577613). > > * This patch **fails Spark unit tests**. > * This patch merges cleanly. > * This patch adds the following public classes _(experimental)_: > * `case class UnschedulableTaskSetAdded(stageId: Int, stageAttemptId: Int)` > * `case class UnschedulableTaskSetRemoved(stageId: Int, stageAttemptId: Int)` > * `case class SparkListenerUnschedulableTaskSetAdded(` > * `case class SparkListenerUnschedulableTaskSetRemoved(` It seems like it fails every time with different test and everyone of them seems transient. @tgravescs I saw a recent change by @HyukjinKwon `SPARK-32245` to run Spark tests as Github actions primarily addressing the transient issues due to jenkins machines slowness. Do you think we should try running these tests using Github Actions? I am not sure how does that work. It would be great if you can help here. ---------------------------------------------------------------- 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]
