1. 29 Jun, 2016 1 commit
    • thomie's avatar
      Testsuite: use ignore_stderr/stdout instead of ignore_output · 1084d375
      thomie authored
      The problem with ignore_output is that it hides errors for WAY=ghci.
      GHCi always returns with exit code 0 (unless it is broken itself).
      For example: ghci015 must have been failing with compile errors for
      years, but we didn't notice because all output was ignored.
      Therefore, replace all uses of ignore_output with either ignore_stderr
      or ignore_stdout. In some cases I opted for adding the expected output.
      Update submodule hpc and stm.
      Reviewed by: simonmar
      Differential Revision: https://phabricator.haskell.org/D2367
  2. 30 Oct, 2015 2 commits
  3. 15 Oct, 2015 1 commit
    • Edward Z. Yang's avatar
      Update Cabal to HEAD, IPID renamed to Component ID. · 5b0191f7
      Edward Z. Yang authored
      This commit contains a Cabal submodule update which unifies installed
      package IDs and package keys under a single notion, a Component ID.
      We update GHC to keep follow this unification.  However, this commit
      does NOT rename installed package ID to component ID and package key to
      unit ID; the plan is to do that in a companion commit.
          - Compiler info now has "Requires unified installed package IDs"
          - 'exposed' is now expected to contain unit keys, not IPIDs.
          - Shadowing is no more.  We now just have a very simple strategy
            to deal with duplicate unit keys in combined package databases:
            if their ABIs are the same, use the latest one; otherwise error.
            Package databases maintain the invariant that there can only
            be one entry of a unit ID.
      Signed-off-by: default avatarEdward Z. Yang <ezyang@cs.stanford.edu>
      Test Plan: validate
      Reviewers: simonpj, austin, bgamari, hvr, goldfire
      Subscribers: thomie
      Differential Revision: https://phabricator.haskell.org/D1184
      GHC Trac Issues: #10714
  4. 27 Nov, 2014 1 commit
  5. 15 Nov, 2014 1 commit
    • Edward Z. Yang's avatar
      Generalize exposed-modules field in installed package database · e14a9732
      Edward Z. Yang authored
      Instead of recording exposed-modules and reexported-modules as seperate
      fields in the installed package database, this commit merges them into
      a single field (exposed-modules).  The motivation for this change is
      in preparation for the inclusion of *signatures* into the installed
      package database, which may also be reexported.  Merging the representation
      means that we can treat reexports uniformly, no matter if they're a normal
      module or a signature.
      This commit adds a stub for signatures, but that code isn't wired up to
      anything yet.
      Contains Cabal submodule update to accommodate these changes.
      Signed-off-by: default avatarEdward Z. Yang <ezyang@cs.stanford.edu>
      Test Plan: validate
      Reviewers: simonpj, duncan, austin
      Subscribers: thomie, carter, simonmar
      Differential Revision: https://phabricator.haskell.org/D421
  6. 26 Jul, 2014 1 commit
    • Edward Z. Yang's avatar
      Module reexports, fixing #8407. · 7f5c1086
      Edward Z. Yang authored
      The general approach is to add a new field to the package database,
      reexported-modules, which considered by the module finder as possible
      module declarations.  Unlike declaring stub module files, multiple
      reexports of the same physical package at the same name do not
      result in an ambiguous import.
      Has submodule updates for Cabal and haddock.
      NB: When a reexport renames a module, that renaming is *not* accessible
      from inside the package.  This is not so much a deliberate design choice
      as for implementation expediency (reexport resolution happens only when
      a package is in the package database.)
      TODO: Error handling when there are duplicate reexports/etc is not very
      well tested.
      Signed-off-by: default avatarEdward Z. Yang <ezyang@cs.stanford.edu>
  7. 21 Jul, 2014 1 commit
    • Edward Z. Yang's avatar
      [ghc-pkg] Fix #5442 by using the flag db stack to modify packages. · d7c807f7
      Edward Z. Yang authored
      Previously, the full database stack was used for ghc-pkg to
      modify packages, which meant that commands like
      'ghc-pkg unregister --user' worked the same as 'ghc-pkg unregister'.
      Since package modification is a "read and write" operation, we
      should use the flag db stack (which is currently used for reads)
      to determine which database to update.
      There is also a new flag --user-package-db, which lets you explicitly
      set the user database (as seen by --user).  This was mostly added
      to aid in testing, but could be useful for end users as well.
      Signed-off-by: default avatarEdward Z. Yang <ezyang@cs.stanford.edu>
      Test Plan: validate
      Reviewers: simonmar, hvr, austin
      Subscribers: simonmar, relrod, carter
      Differential Revision: https://phabricator.haskell.org/D84
  8. 25 Jan, 2013 1 commit
  9. 15 May, 2012 1 commit
  10. 04 Sep, 2011 1 commit
  11. 20 Jul, 2011 1 commit
  12. 25 May, 2011 1 commit
  13. 20 Apr, 2011 1 commit
    • Simon Peyton Jones's avatar
      Add TEST_HC_OPTS to every Makefile invocation of TEST_HC · 6c32ee85
      Simon Peyton Jones authored
      In the testsuite there are numerous Makefiles that invoke $(TEST_HC).
      But, unlike the tests invoked directly by the harness, they didn't pass
      -dno-debug-output, or $(EXTRA_HC_OPTS).
      This patch goes part-way towards the goal of making the two consistent:
      * Almost all invocations in the Makefiles now go
          '$(TEST_HC)' $(TEST_HC_OPTS)
      * In test.mk we initialise
           TEST_HC_OPTS = -dno-debug-output $(EXTRA_HC_OPTS)
      Still to come (I don't know how to do these)
      * The invocations of TEST_HC via cabal are not treated
        (eg cabal01, cabal04), and they should be
      * TEST_HC_OPTS should probably be initialised the same way
        as the Python script computes the flags to pass to the
        TEST_HC that it calls directly
  14. 19 May, 2010 1 commit
  15. 11 Dec, 2009 1 commit
  16. 22 Oct, 2009 1 commit
  17. 21 Oct, 2009 1 commit
  18. 17 Sep, 2009 1 commit
  19. 14 Sep, 2009 1 commit
  20. 10 Sep, 2009 1 commit
  21. 06 Sep, 2009 1 commit
  22. 24 Jul, 2009 1 commit
  23. 26 Apr, 2009 1 commit
  24. 12 Mar, 2009 2 commits
  25. 15 Jan, 2009 1 commit
  26. 08 Jan, 2009 1 commit
  27. 18 Aug, 2008 1 commit
  28. 14 Aug, 2008 1 commit
  29. 13 Aug, 2008 2 commits
  30. 28 Jun, 2008 2 commits
  31. 27 Jun, 2008 1 commit
  32. 11 Feb, 2008 1 commit
  33. 23 Jan, 2008 1 commit
  34. 20 Feb, 2007 1 commit
  35. 27 Jul, 2006 1 commit
  36. 07 Apr, 2006 1 commit