[
https://issues.apache.org/jira/browse/SPARK-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14565847#comment-14565847
]
Andrew Or commented on SPARK-7558:
----------------------------------
Note to self: The following commits must be backported with the original commit:
original - 9eb222c13991c2b4a22db485710dc2e27ccf06dd
hotfix1 - 8c9979337f193c72fd2f1a891909283de53777e3
hotfix2 - a4f24123d8857656524c9138c7c067a4b1033a5e
scalastyle check - 609c4923f98c188bce60ae35c1c8a08a8dfd95f1
> Log test name when starting and finishing each test
> ---------------------------------------------------
>
> Key: SPARK-7558
> URL: https://issues.apache.org/jira/browse/SPARK-7558
> Project: Spark
> Issue Type: Sub-task
> Components: Tests
> Reporter: Patrick Wendell
> Assignee: Andrew Or
> Fix For: 1.5.0
>
>
> Right now it's really tough to interpret testing output because logs for
> different tests are interspersed in the same unit-tests.log file. This makes
> it particularly hard to diagnose flaky tests. This would be much easier if we
> logged the test name before and after every test (e.g. "Starting test XX",
> "Finished test XX"). Then you could get right to the logs.
> I think one way to do this might be to create a custom test fixture that logs
> the test class name and then mix that into every test suite /cc [~joshrosen]
> for his superb knowledge of Scalatest.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
