Skip to content
Snippets Groups Projects
This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. May 05, 2021
  2. May 04, 2021
  3. May 03, 2021
  4. May 02, 2021
    • Emily Pillmore's avatar
      Update CI for cabal-install and cabal-install-solver · bf8dff54
      Emily Pillmore authored
      * Changes needed for GenValidate and release.py to
        accommmodate new solver dependency
      * Bumps bootstrap plans to modern GHC versions
      * Update `validate.sh` and `release.py` to accommodate new solver dep.
      * Update `Makefile` targets
      bf8dff54
    • Emily Pillmore's avatar
      Get HPC working for cabal-install · a54f9d23
      Emily Pillmore authored
      * Strips away dogfooding framework and zinza templates
      * Splits out tests into targets by as a function of running time
      * Delete TESTING.md as it no longer applies
      * Bump cabal-install.cabal to its dev template settings (base >= 4.10,
      Cabal 2.2)
      * Remove Paths_cabal_install (blocks HPC generation)
      * Add `long-tests` target to split out unit-tests and long-running
        DVCS tests.
      a54f9d23
    • Emily Pillmore's avatar
      Move cabal-install-solver to its own toplevel directory · 54696c14
      Emily Pillmore authored
      * Add Setup.hs for `cabal-install-solver`
      * Update `cabal.project` pkg path for `cabal-install-solver`
      54696c14
  5. Apr 26, 2021
  6. Apr 25, 2021
  7. Apr 20, 2021
  8. Apr 18, 2021
  9. Apr 17, 2021
  10. Apr 14, 2021
  11. Apr 13, 2021
  12. Apr 12, 2021
  13. Apr 10, 2021
    • Ollie Charles's avatar
      Fix test --enable-coverage for multi-package projects · 9d16b3ec
      Ollie Charles authored and Ollie Charles's avatar Ollie Charles committed
      Currently, if you have multiple packages in a project and try and run
      the test suite of a single package with --enable-coverage, hpc will fail
      to run. The problem is that _all_ dependencies of the package are built
      with `-fhpc`, but when we run `hpc markup`, we are only passing the
      `.mix` directory of the package being tested. Because we built all
      dependencies with `-fhpc` and we haven't excluded them from the report,
      we need to supply their `.mix` directories too.
      
      The above suggests one fix - compute the transitive closure of all
      `.mix` directories. However, there is another solution - change from
      using an exclude-list to using an include-list. This is the approach
      used in this commit.
      
      Explicitly enumerating all modules to _include_ in the report is simpler
      to code, but is also more likely to be what the user is interested in.
      Generally, when one generates a coverage report from a test-suite, they
      want to understand the coverage of the unit being tested. Having
      coverage information from dependencies is usually not relevant. This is
      also the behavior from old-style Cabal builds, where there wasn't even
      a notion of a Cabal project.
      
      Fixes #5433.
      9d16b3ec
  14. Apr 09, 2021
  15. Apr 08, 2021
  16. Apr 07, 2021
  17. Apr 06, 2021
Loading