[Hackage] #803: cabal test after cabal configure --enable-tests without cabal build creates obscure output

Hackage cvs-ghc at haskell.org
Sun Feb 13 06:06:07 CET 2011


#803: cabal test after cabal configure --enable-tests without cabal build creates
obscure output
----------------------------+-----------------------------------------------
  Reporter:  guest          |        Owner:         
      Type:  defect         |       Status:  new    
  Priority:  normal         |    Milestone:         
 Component:  Cabal library  |      Version:  1.8.0.6
  Severity:  normal         |     Keywords:         
Difficulty:  unknown        |   Ghcversion:         
  Platform:                 |  
----------------------------+-----------------------------------------------
 It wasn't obvious to me that cabal build would be required before cabal
 test. Can cabal test automatically run cabal build? Otherwise a message
 should be shown telling the user to run cabal build.

 Here is an example output
 {{{

 >>> Test suite runtests: RUNNING...
 >>> Test suite runtests: FAIL
 >>> Test suite logged to: dist/test/persistent-0.4.0.1-runtests.log
 >>> Test suite runtests: RUNNING...
 >>> Test suite runtests: FAIL
 >>> Test suite logged to: dist/test/persistent-0.4.0.1-runtests.log
 Test suite runtests: FAIL
 Test suite logged to: dist/test/persistent-0.4.0.1-runtests.log
 0 of 1 test suites (0 of 1 test cases) passed.
 }}}

 The log is exactly the same as the output

-- 
Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/803>
Hackage <http://haskell.org/cabal/>
Hackage: Cabal and related projects



More information about the cabal-devel mailing list