Changes between Version 48 and Version 49 of Building/RunningTests


Ignore:
Timestamp:
Feb 21, 2019 12:43:29 PM (8 months ago)
Author:
davide
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Building/RunningTests

    v48 v49  
    33GHC includes a comprehensive testsuite for catching any regressions.
    44
     5== Using the Testsuite as a developer ==
     6
    57 * [wiki:Building/RunningTests/Running Running the testsuite]
    6   * [wiki:Building/RunningTests/PerformanceTests Performance Tests]
     8 * [wiki:Building/RunningTests/PerformanceTests Performance Tests]
    79 * [wiki:Building/RunningTests/Settings Testsuite Settings and WAYS]
    810 * [wiki:Building/RunningTests/Updating Updating test case results]
    911 * [wiki:Building/RunningTests/Adding Adding new test cases]
    1012 * [wiki:Building/RunningTests/Details Testsuite implementation details]
     13
     14== Using the Testsuite as a user ==
     15
     16
     17In the root directory of the ghc repository or source distribution, run either `make fasttest`, `make test` (which uses the normal speed settings) or `make slowtest` (called `fulltest` in GHC <= 7.10).
     18
     19You should expect that there are no test case failures for the "normal" mode as that is a quality level that all GHC developers are expected to maintain when they check in code. There will usually be some test case failures for the full testsuite run though, and it takes a lot longer to run.
     20
     21The run time of the testsuite can be reduced by running it with multiple threads. For instance if your machine has 8 cores, the following is probably appropriate:
     22{{{
     23$ make test THREADS=8
     24}}}