Changes between Version 35 and Version 36 of Building/RunningTests


Ignore:
Timestamp:
Jul 8, 2011 11:01:14 PM (3 years ago)
Author:
dterei
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Building/RunningTests

    v35 v36  
    2727 * [wiki:Building/RunningTests/Adding Adding new test cases] 
    2828 * [wiki:Building/RunningTests/Details Testsuite implementation details] 
    29  
    30 == Problems running the testsuite == 
    31  
    32  1. If the testsuite fails mysteriously, make sure that the {{{timeout}}} utility is working properly. This Haskell utility is compiled with the stage 1 compiler and invoked by the python driver, which does not print a nice error report if the utility fails. This can happen if, for example, the compiler produces bogus binaries. A workaround is to compile {{{timeout}}} with a stable {{{ghc}}}. 
    33  
    34 == The testsuite and version control branches == 
    35  
    36 It is not clear what to do with the testsuite when branching a compiler; should the testsuite also be branched? 
    37  
    38 If it is not branched then we have the problem that, given a set of tests 
    39 {{{ 
    40 test(tc1, ...) 
    41 test(tc2, ...) 
    42 test(tc3, ...) 
    43 }}} 
    44 if we add first one test, and then another to the HEAD 
    45 {{{ 
    46 test(tc1, ...) 
    47 test(tc2, ...) 
    48 test(tc3, ...) 
    49 test(tc4, ...) 
    50 test(tc5, ...) 
    51 }}} 
    52 and we want to merge `tc5` but not `tc4` to the branch then the merge has to be done by hand, 
    53 as the patch for tc5 depends on the patch for tc4, although most of the files in the patches (`tc5.hs` etc) are disjoint. 
    54  
    55 On the other hand, if it is not branched then any changes in test output mean we need to add extra logic to the test definitions, e.g. 
    56 {{{ 
    57 test(tc5, namebase_if_compiler_lt('ghc','6.9', 'tc5-6.8'), ...) 
    58 }}} 
    59