Uploaded image for project: 'Daffodil'
  1. Daffodil
  2. DAFFODIL-2037

TravisCI results are too verbose

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • None
    • None
    • Infrastructure

    Description

      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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            slawrence Steve Lawrence
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: