Changes between Version 5 and Version 6 of TestingPatches


Ignore:
Timestamp:
Aug 1, 2008 8:45:52 AM (6 years ago)
Author:
simonpj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TestingPatches

    v5 v6  
    1 = Testing Patches = 
     1= Validating Patches = 
    22 
    33Nowadays there are many people working on GHC, which is a Good Thing, but it does mean that many people are inconvenienced if a patch is pushed which makes the HEAD unbuildable. To try to reduce the number of times this happens, we now have a stricter policy for testing patches before committing them. 
     
    55In order to test your patches: 
    66 * Get a repository containing the latest HEAD, the patches you want to push, and no other patches or unrecorded changes. Depending on what you are doing, your working repository might be appropriate; otherwise you might prefer to keep a separate repository just for patch testing. 
    7  * In the root directory of the tree, run `sh validate`. This will do a "quick" build and then run the testsuite in "fast" mode. Do not push if any of the tests give unexpected results! 
     7 
     8 * In the root directory of the tree, run 
     9{{{ 
     10sh validate 
     11}}} 
     12 This will do a "quick" build and then run the testsuite in "fast" mode. Do not push if any of the tests give unexpected results! 
     13 
    814 * Depending on the nature of the changes, more testing might be sensible. e.g. if possible, build system changes should be tested on Linux, Mac OS X and Windows machines.  Look at the full documentation for the [wiki:Building/RunningTests test suite]. 
    915