Github user a-roberts commented on the issue:
https://github.com/apache/spark/pull/14961
Thanks, I did a ctrl-f for "** fail", you'd have a better idea of what the
known flakies are in this farm though, my quick checking:
- using external shuffle service -> looks to be a timeout
These six mention a stopped Spark context (perhaps the previous test
doesn't clean up properly and causes this):
- kryo objects are serialised consistently in different processes ***
FAILED *** (1 minute) -> never seen
- cluster mode, FIFO scheduler *** FAILED *** (1 minute) -> never seen
- cluster mode, fair scheduler *** FAILED *** -> never seen
- verify that correct log urls get propagated from workers *** FAILED ***
(1 minute) -> never seen
- verify that log urls reflect SPARK_PUBLIC_DNS (SPARK-6175) *** FAILED ***
(1 minute) -> never seen
- task throws not serializable exception *** FAILED *** (1 minute) -> never
seen
- simple groupByKey *** FAILED *** (1 minute) [info]
java.lang.NullPointerException:
[info] at org.apache.spark.SparkContext.<init>(SparkContext.scala:552) >
different causes now, never seen
- onTaskGettingResult() called when result fetched remotely *** FAILED ***
(135 milliseconds) -> never seen
- set spark.sql.warehouse.dir *** FAILED *** (5 minutes, 0 seconds) ->
never seen
- set hive.metastore.warehouse.dir *** FAILED *** (10 seconds, 552
milliseconds) -> never seen
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
