Github user srowen commented on the issue: https://github.com/apache/spark/pull/17923 Oh @fjh100456 actually this test failure is legitimate, not due to recent Jenkins problems. The UI test needs to reflect the new display. `Cause: org.scalatest.exceptions.TestFailedException: "[2]/2 (1 failed)" was not equal to "[3]/2 (1 failed)"`
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org