diff options
| author | Imran Rashid <irashid@cloudera.com> | 2015-12-16 19:01:05 -0800 |
|---|---|---|
| committer | Andrew Or <andrew@databricks.com> | 2015-12-16 19:01:05 -0800 |
| commit | 38d9795a4fa07086d65ff705ce86648345618736 (patch) | |
| tree | 904c355814df2c188a752c917ba013646a282b13 /scalastyle-config.xml | |
| parent | ce5fd4008e890ef8ebc2d3cb703a666783ad6c02 (diff) | |
| download | spark-38d9795a4fa07086d65ff705ce86648345618736.tar.gz spark-38d9795a4fa07086d65ff705ce86648345618736.tar.bz2 spark-38d9795a4fa07086d65ff705ce86648345618736.zip | |
[SPARK-10248][CORE] track exceptions in dagscheduler event loop in tests
`DAGSchedulerEventLoop` normally only logs errors (so it can continue to process more events, from other jobs). However, this is not desirable in the tests -- the tests should be able to easily detect any exception, and also shouldn't silently succeed if there is an exception.
This was suggested by mateiz on https://github.com/apache/spark/pull/7699. It may have already turned up an issue in "zero split job".
Author: Imran Rashid <irashid@cloudera.com>
Closes #8466 from squito/SPARK-10248.
Diffstat (limited to 'scalastyle-config.xml')
0 files changed, 0 insertions, 0 deletions