This project is mirrored from Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
  1. 05 Dec, 2016 1 commit
    • Tamar Christina's avatar
      Color output is wreaking havoc on test results · 847d2293
      Tamar Christina authored
      D2716 introduced colors into the output of GHC.
      These color ourputs are done using escape characters output
      to the terminal.
      These however are wreaking havoc on the testsuite output as now
      no stderr with a warning or error will match anymore.
      Instead of accepting the new codes as expected values instead I
      turn them off. So the testsuite is consistent on platforms/terminals we
      don't support colors on.
      Test Plan:
      any test that outputs colors. e.g.
      make test TEST=T9576
      Reviewers: austin, Rufflewind, bgamari
      Subscribers: thomie, #ghc_windows_task_force
      Differential Revision:
      GHC Trac Issues: #8809
  2. 01 Oct, 2016 1 commit
  3. 20 Jun, 2016 3 commits
  4. 18 Jun, 2016 2 commits
  5. 25 May, 2016 2 commits
  6. 24 May, 2016 1 commit
  7. 17 May, 2016 1 commit
  8. 30 Apr, 2016 1 commit
  9. 29 Feb, 2016 1 commit
  10. 27 Feb, 2016 1 commit
    • Herbert Valerio Riedel's avatar
      Default to -fno-show-warning-groups (re #10752) · 46f3775c
      Herbert Valerio Riedel authored
      As `-fno-show-warning-groups` shows associated warning groups regardless
      of whether the respective warning group flag as been passed on the CLI,
      the warning-group information may be confusing to users.
      At this point, `-fshow-warning-groups` is useful mostly to GHC
      developers and possibly GHC users who want to see which warning groups
      an emitted warning is part of. (Btw, this is particularly interesting in
      combination with `-Weverything` which enables *every* warning flag known
      to GHC.)
      Consequently, starting with this commit, one has to opt-in via
      `-fshow-warning-groups` for GHC to show warning groups.
      In order to reduce the testsuite delta in this commit, the
      `-fshow-warning-groups` flag has been added to TEST_HC_OPTS.
  11. 23 Feb, 2016 1 commit
  12. 03 Nov, 2015 1 commit
  13. 04 Oct, 2015 1 commit
  14. 02 Sep, 2015 2 commits
  15. 17 Aug, 2015 1 commit
  16. 09 Jun, 2015 1 commit
    • thomie's avatar
      Revert "The test runner now also works under the msys-native Python." · bb996712
      thomie authored
      To make the test runner work under msys-native Python...
      Commit 5258566e broke the msys testsuite
      driver (#10441). It changed the quoting of `config.compiler` from single
      quotes to double quote, which turns out to not be compatible with what
      the function `passThroughCmd` expected.
      We could fix `passThroughCmd` to handle the case where `config.compiler`
      is double quoted, and scatter some notes around to make sure the quoting
      done in various places of the testsuite driver stay compatible.
      Instead, this commit reverts 101c62e2,
      which introdced the function `passThroughCmd` in the first place
      (#9626). ezyang reports that doing this revert fixes the testsuite
      driver for him using the the following version of msys2:
        msys2-keyring r8.3864337-1
      Ideally we'd know what minimum version of msys2 we require, but for now
      this fix is better than nothing.
      Only gintas ever reported the original problem, and he actually
      mentioned shortly afterwards: "This may have been fixed by a recent
      release of msys2, but I am not sure."
      Differential Revision:
  17. 04 Jun, 2015 1 commit
    • thomie's avatar
      Make validate more quiet · d0063e89
      thomie authored
        * By default use V=0, and call the testsuite with VERBOSE=2, which we
          did before only with validate --quiet. This disables printing the
          test commands it runs.
        * When --quiet is used, call the testsuite with VERBOSE=1. This
          disables printing the '====> Scanning' lines, and doesn't print
          which test is being run. So it only prints something when a test
          accidentally prints to stdout or when it fails.
          Don't set this option on Travis, as Travis will cancel a build if it
          doesn't see any output for more than 10 minutes.
        * When --quiet is used, set the new test option NO_PRINT_SUMMARY,
          which skips printing the test summary. Only the list of unexpected
          failures is printed, if there are any. Note that the full summary
          can still be found in testsuite_summary.txt
        * When --quiet is used, don't pass the `-v` flag to `ghc-pkg check`
        * When --quiet is used, don't print the Oops! header. It shoud be
          clear from the list of failing tests that something is wrong.
      This is all done to get the most out of 30 lines of logfile. These changes can
      be disabled later by simply not passing the --quiet flag to validate.
      Differential Revision:
  18. 28 May, 2015 1 commit
    • thomie's avatar
      Testdriver: do not interfer with MinGW path magic (#10449) · ce166a3a
      thomie authored
      This should fix the testsuite driver on Windows using the MinGW tools
      with a native build of Python.
      MinGW automagically converts MinGW-style paths (e.g.
      '/c/programs/ghc/bin/ghc') into ordinary Windows paths (e.g.
      'C:/programs/ghc/bin/ghc') when a native Windows program is invoked. But
      it doesn't do so when those paths are wrapped with a pair of escaped
      double quotes.
      The fix is to not call `eval` on the paths in Python, which let's us use
      one less pair of quotes, and makes MinGW happy.
      Reviewers: Rufflewind, austin
      Differential Revision:
  19. 23 May, 2015 1 commit
  20. 11 Mar, 2015 1 commit
  21. 02 Mar, 2015 1 commit
    • thomie's avatar
      `make test` in root directory now runs fulltest · 31d4f2e9
      thomie authored
      Currently, running `make test` in:
        /                   runs fast testsuite
        /testsuite          doesn't work
        /testsuite/tests    runs slow testsuite
      This commit:
        * changes `make test` in the ghc root directory to run the slow testsuite,
          just like it already does in `testsuite/tests`
        * adds some simple targets to `/testsuite`, that all delegate to
        * adds a new target `fasttest` to the toplevel Makefile, with a shorthand
          name `fast` (for consistency with /testsuite and /testsuite/tests)
        * declares some more targets PHONY for safety
      Wiki pages that need updating:
        * Building/StandardTargets
        * Buliding/RunningTests
      Reviewers: austin
      Reviewed By: austin
      Subscribers: thomie
      Differential Revision:
  22. 21 Oct, 2014 1 commit
    • mlen's avatar
      Enabled warn on tabs by default (fixes #9230) · 972ba121
      mlen authored
      This revision enables -fwarn-tabs by default and add a suppression
      flag, so that GHC compilation won't fail when some files contain tab
      Test Plan: Additional test case, T9230, was added to cover that change.
      Reviewers: austin
      Reviewed By: austin
      Subscribers: simonmar, ezyang, carter, thomie, mlen
      Differential Revision:
      GHC Trac Issues: #9230
  23. 23 Aug, 2014 1 commit
    • Sergei Trofimovich's avatar
      testsuite: disable gcc's warnings about casts of incompatible prototypes in UNREG · fcdd58d2
      Sergei Trofimovich authored
      Haskell's 'foreign import' declaraion does not have a way
      to extress exact C prototypes (it ignores 'const' modifiers, exact pointer
      types, etc.) which leads to warnings when C backend generates calls to such
               warning: conflicting types for built-in function ‘strlen’ [enabled by default]
      Patch disables builtin functions for UNREG build
      to workaround test failures due to stderr mismatch.
      Fixes the following test failures:
          TEST="safePkg01 T5423 T7574 T3736"
      Signed-off-by: default avatarSergei Trofimovich <>
  24. 23 May, 2014 1 commit
    • Joachim Breitner's avatar Be liberal in accepting GHC_PKG output · 864759cb
      Joachim Breitner authored
      When the tree is not built, GHC_PKG refers to ghc-pkg in the patth,
      which may not yet support --simple-output to suppress the field name. So
      we strip the fieldname when parsing the output, to avoid annoying
  25. 05 Oct, 2013 1 commit
    • Joachim Breitner's avatar
      Flag to test suite: SKIP_PERF_TESTS · 718e86b4
      Joachim Breitner authored
      More often than not the output of the performance tests is in the way,
      rather than helping. This allows the use of `make SKIP_PERF_TESTS=YES`
      to skip these tests. Fixes #8413
  26. 20 Sep, 2013 1 commit
    • Joachim Breitner's avatar
      Test driver: Implement different verbosities · 1e246965
      Joachim Breitner authored
      Select verbosity with "make VERBOSE=n". Options so far:
       n=0: No per-test output
       n=1: Only failing test results
       n=2: As above, plus progress information (names of all tests)
       n=3: As aobve, plus commands called.
      Default currently is n=3, although n=2 might be a nicer default.
  27. 17 Sep, 2013 1 commit
  28. 20 Jun, 2013 1 commit
  29. 12 May, 2013 1 commit
    •'s avatar
      Change how we detect what library ways are available · 962fd59e authored
      We used to use the base package to do the detection. However, base has
          extra-lib-dirs: @ICONV_LIB_DIRS@
      in, which means that if ICONV_LIB_DIRS is set then
      the package config will have
          library-dirs: [...]base/dist-install/build /path/for/iconv
      and, as paths may be double quoted and contains spaces, this makes it
      a little tricky to extra the path that we want to look in (the first
      We therefore now use the ghc-prim package, which has no such complication.
  30. 10 May, 2013 2 commits
  31. 21 Apr, 2013 2 commits
  32. 15 Mar, 2013 1 commit
  33. 11 Feb, 2013 1 commit
    •'s avatar
      Add 'make list_brokens' · 3d94d01a authored
      Gives a list of tickets that the testsuite thinks are broken, and
      what bug it thinks is the reason. This can then be pasted into trac
      and 'previewed', which will show any closed tickets with strikeout.