Changes between Version 10 and Version 11 of Building/RunningTests


Ignore:
Timestamp:
Oct 21, 2007 10:12:45 PM (8 years ago)
Author:
igloo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Building/RunningTests

    v10 v11  
    442442
    443443 1. If the test suite 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}}}.
     444
     445= The testsuite and branches =
     446
     447It is not clear what to do with the testsuite when branching a compiler; should the testsuite also be branched?
     448
     449If it is not branched then we have the problem that, given a set of tests
     450{{{
     451test(tc1, ...)
     452test(tc2, ...)
     453test(tc3, ...)
     454}}}
     455if we add first one test, and then another to the HEAD
     456{{{
     457test(tc1, ...)
     458test(tc2, ...)
     459test(tc3, ...)
     460test(tc4, ...)
     461test(tc5, ...)
     462}}}
     463and we want to merge `tc5` but not `tc4` to the branch then the merge has to be done by hand,
     464as the patch for tc5 depends on the patch for tc4, although most of the files in the patches (`tc5.hs` etc) are disjoint.
     465
     466On 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.
     467{{{
     468test(tc5, namebase_if_compiler_lt('ghc','6.9', 'tc5-6.8'), ...)
     469}}}