1. 29 Feb, 2020 1 commit
  2. 11 Dec, 2019 1 commit
  3. 30 Nov, 2019 1 commit
  4. 08 Oct, 2019 1 commit
  5. 16 Sep, 2019 1 commit
  6. 24 May, 2019 1 commit
    • Alp Mestanogullari's avatar
      add an --hadrian mode to ./validate · 04b4b984
      Alp Mestanogullari authored
      When the '--hadrian' flag is passed to the validate script, we use hadrian
      to build GHC, package it up in a binary distribution and later on run GHC's
      testsuite against the said bindist, which gets installed locally in the process.
      Along the way, this commit fixes a typo, an omission (build iserv binaries
      before producing the bindist archive) and moves the Makefile that enables
      'make install' on those bindists from being a list of strings in the code to
      an actual file (it was becoming increasingly annoying to work with).
      Finally, the Settings.Builders.Ghc part of this patch is necessary for being
      able to use the installed binary distribution, in 'validate'.
  7. 25 Mar, 2019 1 commit
    • Takenobu Tani's avatar
      Update Wiki URLs to point to GitLab · 3769e3a8
      Takenobu Tani authored
      This moves all URL references to Trac Wiki to their corresponding
      GitLab counterparts.
      This substitution is classified as follows:
      1. Automated substitution using sed with Ben's mapping rule [1]
          Old: ghc.haskell.org/trac/ghc/wiki/XxxYyy...
          New: gitlab.haskell.org/ghc/ghc/wikis/xxx-yyy...
      2. Manual substitution for URLs containing `#` index
          Old: ghc.haskell.org/trac/ghc/wiki/XxxYyy...#Zzz
          New: gitlab.haskell.org/ghc/ghc/wikis/xxx-yyy...#zzz
      3. Manual substitution for strings starting with `Commentary`
          Old: Commentary/XxxYyy...
          New: commentary/xxx-yyy...
      See also !539
      [1]: https://gitlab.haskell.org/bgamari/gitlab-migration/blob/master/wiki-mapping.json
  8. 15 Oct, 2018 1 commit
    • Krzysztof Gogolewski's avatar
      Cleanup boot and validate · a816ac48
      Krzysztof Gogolewski authored
      - Remove dph from validate; dph was removed
      - The required-tag argument to boot was used only for dph, remove
      - check_boot_packages() was not called at all, and didn't work.
        I fixed it based on previous Perl version.
      Test Plan: Harbormaster
      Reviewers: bgamari, thomie
      Reviewed By: bgamari
      Subscribers: rwbarton, carter
      Differential Revision: https://phabricator.haskell.org/D5129
  9. 06 Jul, 2018 1 commit
  10. 02 Jun, 2018 1 commit
    • Ben Gamari's avatar
      vectorise: Put it out of its misery · faee23bb
      Ben Gamari authored
      Poor DPH and its vectoriser have long been languishing; sadly it seems there is
      little chance that the effort will be rekindled. Every few years we discuss
      what to do with this mass of code and at least once we have agreed that it
      should be archived on a branch and removed from `master`. Here we do just that,
      eliminating heaps of dead code in the process.
      Here we drop the ParallelArrays extension, the vectoriser, and the `vector` and
      `primitive` submodules.
      Test Plan: Validate
      Reviewers: simonpj, simonmar, hvr, goldfire, alanz
      Reviewed By: simonmar
      Subscribers: goldfire, rwbarton, thomie, mpickering, carter
      Differential Revision: https://phabricator.haskell.org/D4761
  11. 02 Oct, 2017 1 commit
    • Ben Gamari's avatar
      Rewrite boot in Python · c0e6c734
      Ben Gamari authored
      One step closer to being able to drop the Windows Perl tarball. We
      previously attempted to do this in D3567 but were forced to revert due
      to Windows problems.
       * @Phyx kindly contributed the codepath allowing this to work on
      Test Plan: Validate
      Reviewers: hvr, austin, Phyx
      Subscribers: erikd, thomie, rwbarton
      Differential Revision: https://phabricator.haskell.org/D3918
  12. 28 Jul, 2017 1 commit
  13. 26 May, 2017 1 commit
  14. 22 May, 2017 1 commit
  15. 05 Apr, 2017 1 commit
    • Ben Gamari's avatar
      validate: Clean GMP trees · 53152236
      Ben Gamari authored
      For reasons unknown `validate` passed `NO_CLEAN_GMP=YES` to
      `maintainer-clean`, leaving a stale `gmp.h` which causes the build to
      fail in the event that the uses a tree for validating for two different
      target platforms. This is quite unexpected, don't do it.
      Reviewers: hvr, austin, rwbarton, dfeuer
      Reviewed By: dfeuer
      Subscribers: thomie
      Differential Revision: https://phabricator.haskell.org/D3409
  16. 17 Oct, 2016 1 commit
  17. 02 Oct, 2016 1 commit
  18. 18 Jun, 2016 3 commits
  19. 17 Apr, 2016 1 commit
  20. 17 Jan, 2016 1 commit
  21. 04 Jan, 2016 1 commit
    • thomie's avatar
      Build system: delete ghc-pwd · 4c56ad36
      thomie authored
      On Windows, with msys2, `pwd` works (as can be seen by the use of `pwd`
      that slipped into the validate script), so there is really no need for
      `ghc-pwd` anymore.
      Test Plan: try it
      Reviewers: austin, bgamari, Phyx
      Reviewed By: Phyx
      Subscribers: Phyx, erikd
      Differential Revision: https://phabricator.haskell.org/D1731
  22. 24 Nov, 2015 1 commit
  23. 29 Oct, 2015 1 commit
    • thomie's avatar
      Revert "Build system: don't create mk/are-validating.mk" · fa587316
      thomie authored
      This reverts commit aecf4a5f.
      It turns out the Simons are relying on 'mk/are-validating.mk', see
      The workflow they are using is:
        * run ./validate
        * find a bug in the compiler
        * try to fix the bug, running 'make 1' (or 'make 2') repeatedly. Because
          of 'mk/are-validating.mk', this uses the same build settings as validate.
        * continue ./validate (--no-clean)
      I suggested two alternatives:
        A. run 'make 1 Validating=YES' instead of 'make 1'
           Problem: when running `./validate --fast` or `./validate --hpc`
           instead of a normal `./validate`, validate sets ValidateSpeed and
           ValdateHpc in mk/are-validating.mk. You would for example have to run
           'make 1 Validating=YES ValidateSpeed=FAST' instead of 'make 1' to get the
           same build settings as `./validate --fast`, which is entirely too long and
           error prone.
        B. uncomment `#BuildFlavour=validate` in mk/build.mk, and include
            * any other settings you have in build.mk will also get used.
            * the distinction between 'mk/validate.mk' and 'mk/build.mk' becomes less
            * it is easy to forget to include 'mk/validate.mk'.
            * the build system again doesn't have access to the ValidateSpeed and
              ValdateHpc settings set by validate.
      Neither of these two options is entirely satisfactory.
      Reviewers: austin, bgamari
      Differential Revision: https://phabricator.haskell.org/D1383
  24. 04 Oct, 2015 1 commit
  25. 08 Sep, 2015 1 commit
    • thomie's avatar
      Build system: delete the InstallExtraPackages variable · a1586074
      thomie authored
      Just install all packages that are built. Don't make an exception for
      the dph and extra packages.
      You can control whether the dph and extra packages should be build using
      the variables BUILD_DPH and BUILD_EXTRA_PKGS. These variables didn't
      exist before. But now that they do, InstallExtraPackages isn't really
      needed anymore.
      Reviewed by: austin
      Differential Revision: https://phabricator.haskell.org/D1227
  26. 02 Sep, 2015 1 commit
    • thomie's avatar
      Testsuite: by default run all tests for a single way · c43c8e2c
      thomie authored
      `make test` now runs all tests for a single way only. Use `make slowtest` to
      get the previous behaviour (i.e. run all tests for all ways).
      The intention is to use this new `make test` setting for Phabricator, as
      a reasonable compromise between `make fasttest` (what it previously
      used) and a fullblown `make slowtest` (which runs all tests for all
      See Note [validate and testsuite speed] in toplevel Makefile.
      Differential Revision: https://phabricator.haskell.org/D1178
  27. 20 Aug, 2015 1 commit
  28. 17 Aug, 2015 1 commit
  29. 22 Jul, 2015 1 commit
  30. 21 Jul, 2015 2 commits
  31. 13 Jul, 2015 1 commit
    • thomie's avatar
      Build system: do not build stm and parallel by default · 392ff06d
      thomie authored
      stm and parallel have an 'extra' tag in the ./packages file, so would get
      added to PACKAGES_STAGE2 by default, and subsequently build by the stage2
      With this patch, this happens only when you set BUILD_EXTRA_PKGS=YES in
      build.mk. A normal validate still builds (and tests) the 'extra'
      packages, but they are skipped for `validate --fast`. Maybe this brings
      us closer to finishing within the 50 minute Travis limit as well.
      We can later try to give random, primitive and vector an 'extra' tag as
      well (now they have a 'dph' tag), but some tests will probably fail at
      Differential Revision: https://phabricator.haskell.org/D1065
  32. 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: https://phabricator.haskell.org/D942
  33. 07 Apr, 2015 1 commit
  34. 01 Apr, 2015 1 commit
  35. 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: https://phabricator.haskell.org/D685
  36. 18 Nov, 2014 1 commit
  37. 07 Nov, 2014 1 commit