Changes between Version 7 and Version 8 of TestingPatches


Ignore:
Timestamp:
Aug 26, 2008 5:08:28 PM (6 years ago)
Author:
simonpj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TestingPatches

    v7 v8  
    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.  
    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.  
    23 These flags, and others understood by `validate` are documented in the `validate` script itself. 
     20== More details on validation == 
     21 
     22`validate` usually starts by `make distclean` to make sure that everything builds from scratch.  Furthermore, it ignores the build settings you have put in `mk/build.mk`, and instead uses those in `mk/validate-settings.mk`.  (It does not mess up your `mk/build.mk` file of course.) 
     23 
     24After you run `validate` your tree will continue to use the same settings. The way to get back to using your own `build.mk` is to run `make distclean`.  Less brutally, simply remove the file `mk/are-validating.mk`. 
     25 
     26In order to save time while debugging problems revealed by validate, the validate script understands several flags. These flags, and others understood by `validate` are documented in the `validate` script itself. 
     27  * '''`--no-clean`''':  validate will not clean the tree before starting, so it will continue a previous build.  
     28  * '''`--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.  
    2429 
    2530'''Important:''' When using either of these flags, be careful that you don't end up pushing patches that have not been properly validated! 
     31 
     32 
    2633 
    2734== Testing different configurations ==