[
https://issues.apache.org/jira/browse/DAFFODIL-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Lawrence resolved DAFFODIL-2037.
--------------------------------------
Resolution: Won't Fix
We have switched to GitHub actions since this was opened, which makes it fairly
easy to view CI output. We have also improved SBT configuration so tsets only
output of failure, so the output is much less verbose than it used to be. No
need to make any changes. Resolving as won't fix.
> 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
> Labels: beginner
>
> 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.20.10#820010)
