Changes between Version 2 and Version 3 of Building/RunningTests/Details


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

--

Legend:

Unmodified
Added
Removed
Modified
  • Building/RunningTests/Details

    v2 v3  
    130130either 'pass' or 'fail' indicating that the test passed or failed 
    131131respectively. 
     132 
     133== The testsuite and version control branches == 
     134 
     135It is not clear what to do with the testsuite when branching a compiler; should the testsuite also be branched? 
     136 
     137If it is not branched then we have the problem that, given a set of tests 
     138{{{ 
     139test(tc1, ...) 
     140test(tc2, ...) 
     141test(tc3, ...) 
     142}}} 
     143if we add first one test, and then another to the HEAD 
     144{{{ 
     145test(tc1, ...) 
     146test(tc2, ...) 
     147test(tc3, ...) 
     148test(tc4, ...) 
     149test(tc5, ...) 
     150}}} 
     151and we want to merge `tc5` but not `tc4` to the branch then the merge has to be done by hand, 
     152as the patch for tc5 depends on the patch for tc4, although most of the files in the patches (`tc5.hs` etc) are disjoint. 
     153 
     154On 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. 
     155{{{ 
     156test(tc5, namebase_if_compiler_lt('ghc','6.9', 'tc5-6.8'), ...) 
     157}}}