You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@daffodil.apache.org by "Steve Lawrence (JIRA)" <ji...@apache.org> on 2019/08/05 12:42:00 UTC

[jira] [Commented] (DAFFODIL-2187) too many debug/oolagdebug messages from sbt it:test

    [ https://issues.apache.org/jira/browse/DAFFODIL-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900051#comment-16900051 ] 

Steve Lawrence commented on DAFFODIL-2187:
------------------------------------------

This is semi related to DAFFODIL-2037, which is a bit more general. Ideally we would modify the sbt configuration so that 'sbt test' and 'sbt it:test' only display the output of a test when the test fails. So we could still output all this nasty debug information, but it won't clutter things unless it fails. Unfortunately, an sbt bug (mentioned in DAFFODIL-2037) prevents that from working. Disabling theses test might be a decent workaround until that bug is fixed.

> too many debug/oolagdebug messages from sbt it:test
> ---------------------------------------------------
>
>                 Key: DAFFODIL-2187
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2187
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Infrastructure, QA
>    Affects Versions: 2.4.0
>            Reporter: Michael Beckerle
>            Priority: Major
>             Fix For: 2.5.0
>
>
> The volume of output created by sbt it:test is so large that when something fails in a travis CI build, it is almost impossible to see what went wrong.
> Most of this output is created by tests that turn on various levels of logging that really aren't relevant any more.
> Tests that turn on debug or oolagdebug level of detail should be revisited to see whether they should still be run with those settings off, or just disabled.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)