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

Posted to commits@daffodil.apache.org by "Steve Lawrence (Jira)" <ji...@apache.org> on 2021/02/04 20:33:00 UTC

[jira] [Updated] (DAFFODIL-2037) TravisCI results are too verbose

     [ https://issues.apache.org/jira/browse/DAFFODIL-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Lawrence updated DAFFODIL-2037:
-------------------------------------
    Priority: Minor  (was: Major)

> TravisCI results are too verbose
> --------------------------------
>
>                 Key: DAFFODIL-2037
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2037
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Infrastructure
>            Reporter: Steve Lawrence
>            Priority: Minor
>
> We run lots of tests with TravisCI and it results in lots of output. So when something does fail on TravisCI it can be very difficult to figure out what the actual problem is. And TravisCI only show the first 10,000 lines, os if the the error was after that you need to download the full log.
> You're suposed to be able to to run ``sbt -error COMMANDS`` to only show errors, but there is currently a bug in SBT where running tests ignores that: https://github.com/sbt/sbt/issues/4480.  A workaround is posted in that thread. We should implement that so that we can reduce the TravisCI cluter. Also, we should modify the JUnit interface options so that test output is only displayed when a test fails.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)