Changes between Version 6 and Version 7 of TestingPatches


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

--

Legend:

Unmodified
Added
Removed
Modified
  • TestingPatches

    v6 v7  
    1818Assuming 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. 
    1919 
    20 In 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! 
     20In order to save time while debugging problems revealed by validate, the validate script understands a couple of flags.  
     21  * If you run `sh validate --no-clean` then validate will not clean the tree before starting, so it will continue a previous build.  
     22  * 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.  
     23These flags, and others understood by `validate` are documented in the `validate` script itself. 
     24 
     25'''Important:''' When using either of these flags, be careful that you don't end up pushing patches that have not been properly validated! 
    2126 
    2227== Testing different configurations ==