Changes between Version 4 and Version 5 of TestingPatches


Ignore:
Timestamp:
Mar 5, 2008 4:22:26 PM (6 years ago)
Author:
igloo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TestingPatches

    v4 v5  
    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  * Run the validate script in the root of the tree. 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 * 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! 
    88 * 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]. 
    99 
     
    1111 
    1212Assuming all is well, go ahead and commit your changes! If you have commit access then just push as normal. If not, use "darcs send --edit-description" and add a note to say what testing you have done, and on which operating system/architecture. 
     13 
     14In order to save time while debugging problems revealed by validate, the validate script understands a couple of flags. If you run `sh validate --no-clean` then validate will not clean the tree before starting, so it will continue a previous build. If you run `sh validate --testsuite-only` then validate will not build the tree at all, but only run the testsuite. This is useful if the problems validate found were only due to the testsuite falling out of sync with the code. '''Important:''' When using either of these flags, be careful that you don't end up pushing patches that have not been properly validated! 
    1315 
    1416== Testing different configurations ==