[jira] [Commented] (SPARK-38089) Improve assertion failure message in TestUtils.assertExceptionMsg
[ https://issues.apache.org/jira/browse/SPARK-38089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17486025#comment-17486025 ] Apache Spark commented on SPARK-38089: -- User 'xkrogen' has created a pull request for this issue: https://github.com/apache/spark/pull/35383 > Improve assertion failure message in TestUtils.assertExceptionMsg > - > > Key: SPARK-38089 > URL: https://issues.apache.org/jira/browse/SPARK-38089 > Project: Spark > Issue Type: Improvement > Components: Spark Core, Tests >Affects Versions: 3.2.1 >Reporter: Erik Krogen >Priority: Major > > {{TestUtils.assertExceptionMsg}} is great, but when the assertion _doesn't_ > match, it can be challenging to tell why, because the exception tree that was > searched isn't printed. Only way I could find to fix it up was to run things > in a debugger and check the exception tree. > It would be very helpful if {{assertExceptionMsg}} printed out the exception > tree in which it was searching (upon failure). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-38089) Improve assertion failure message in TestUtils.assertExceptionMsg
[ https://issues.apache.org/jira/browse/SPARK-38089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17486027#comment-17486027 ] Apache Spark commented on SPARK-38089: -- User 'xkrogen' has created a pull request for this issue: https://github.com/apache/spark/pull/35383 > Improve assertion failure message in TestUtils.assertExceptionMsg > - > > Key: SPARK-38089 > URL: https://issues.apache.org/jira/browse/SPARK-38089 > Project: Spark > Issue Type: Improvement > Components: Spark Core, Tests >Affects Versions: 3.2.1 >Reporter: Erik Krogen >Priority: Major > > {{TestUtils.assertExceptionMsg}} is great, but when the assertion _doesn't_ > match, it can be challenging to tell why, because the exception tree that was > searched isn't printed. Only way I could find to fix it up was to run things > in a debugger and check the exception tree. > It would be very helpful if {{assertExceptionMsg}} printed out the exception > tree in which it was searching (upon failure). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org