This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 19 Dec, 2014 1 commit
    • Christiaan Baaij's avatar
      Always setup (DY)LD_LIBRARY_PATH for testsuite · 2158e3c9
      Christiaan Baaij authored
      Now that Cabal is in charge of RPATH handling on certain OS',
      we must always setup a correct (DY)LD_LIBRARY_PATH when
      running the testsuite. Not just when we are building relocatable
      packages.
      
      The "problem" is, is that Cabal now adds an RPATH pointing
      to the installation location of the library. However, during
      testing, the library won't be there yet. We much hence setup
      a (DY)LD_LIBRARY_PATH that includes the dist/build dir.
      2158e3c9
  2. 18 Dec, 2014 1 commit
  3. 12 Dec, 2014 3 commits
  4. 10 Dec, 2014 1 commit
    • Luite Stegeman's avatar
      use CompilerInfo rather than CompilerId for resolving flags and · 7d91b773
      Luite Stegeman authored
      path templates.
      
      CompilerInfo contains more information about the compiler than
      CompilerId, which just stores the flavour and version. In particular,
      CompilerInfo knows an AbiTag, which can be used to tell binary
      incompatible results from the same compiler apart, and detailed
      information about supported languages and extensions.
      
      Some fields in CompilerInfo may be left unknown (Nothing). This can
      be used in the future to allow partially resolving configurations
      based on supported languages or extensions.
      7d91b773
  5. 14 Sep, 2014 2 commits
  6. 20 Aug, 2014 1 commit
  7. 04 Aug, 2014 1 commit
  8. 20 May, 2014 2 commits
    • ttuegel's avatar
      Always stream test output concurrently · e7236056
      ttuegel authored
      Issue #1810. Some test suites would freeze if invoked with
      `--show-details=always` instead of `--show-details=streaming` because
      output would build up in the pipe without being cleared. This corrects
      the issue by forcing the length of the output string in another thread.
      
      (cherry picked from commit e5a07013)
      e7236056
    • ttuegel's avatar
      Always stream test output concurrently · e5a07013
      ttuegel authored
      Issue #1810. Some test suites would freeze if invoked with
      `--show-details=always` instead of `--show-details=streaming` because
      output would build up in the pipe without being cleared. This corrects
      the issue by forcing the length of the output string in another thread.
      e5a07013
  9. 19 Mar, 2014 2 commits
    • ttuegel's avatar
      Implement '--show-details=streaming' for ExeV10 tests · ca3e1dac
      ttuegel authored
      LibV09 tests are still non-streaming because those tests do not use
      stdout anyway.
      ca3e1dac
    • ttuegel's avatar
      Refactor test runners · 8083ca4b
      ttuegel authored
      The test runners for exitcode-stdio and detailed tests will be separated
      into their own modules. They cannot share a test runner because
      '--show-details=streaming' does not make sense for detailed tests the
      way they are implemented now. The detailed test runner needs to be
      substantially rewritten anyway, so splitting up the test runners will
      eventually accomodate that goal.
      8083ca4b