GitLab

I fixed this in a plausible looking way, similar to compiler_stats_range/num fields.

Signed-off-by: Edward Z. Yang <ezyang@mit.edu>

This handles the case where we redirect stdout/stderr to a file, but
the command fails quickly and the file is not actually created.

Added an option to combine stdout and stderr into a single file. This is
useful for ghci scripts that produce interleaved errors and normal
output.

Also modified check_stderr_ok so that it normalizes stderr in the same
way as compile tests.

This makes it much easier to update the bounds.  Instead of coming up
with a suitable (min,max) pair, you just give e.g. (base, 10) to allow
10% deviation from the base figure, which can be pasted from the
error.

e.g. previously:

-      # expected value: 458700632 (amd64/Linux):
-      if_wordsize(64,
-          compiler_stats_num_field('bytes allocated', 440000000,
-                                                      480000000)),

now:

+      if_wordsize(64, # sample from amd64/Linux 15/2/2012
+          compiler_stats_range_field('bytes allocated', 360243576, 10)),

Note: use stats_range_field rather than stats_num_field.  I left
support for the old way for now so that we can do a gradual migration.

(next I suppose we should make it so that 'make accept' works for perf
tests, but that's for another day)

Motivation: we wanted to disable -dcore-lint for the perf tests

OVERALL SUMMARY for test run started at Fri Jan  6 09:46:46 GMT 2012
      82 total tests, which gave rise to
     820 test cases, of which
       0 caused framework failures
     818 were skipped

       0 expected passes
       2 had missing libraries  <---
       0 expected failures
       0 unexpected passes
       0 unexpected failures

Required by the changes to GHC to generate main() when linking.

The default setting for only_ways was [], which meant "all ways".
However, it's really useful to have [] mean "no ways".

In cgrun057 I used only_ways(prof_ways) to mean "only run this in the
profiling ways", but if profiling is disabled then prof_ways = [] and
this doesn't do what we want.  Profiling is normally disabled in
validate, but I had it enabled because I was testing profiling.

So now only_ways defaults to None, which means "all ways", and [] now
means "no ways".

Fixes various Windows test failures (T3103, plugins04)

It is in general illegible (e.g. all newlines have been removed), and
in the rare cases you really need it then you can diff the normalised
outputs manually.

To add a sample profile, create a file <test>.prof.sample.  The test
driver normalises the file to remove the actual data (timing and
allocations), so that the test will compare the shape of the profile
and the entry counts only.

They added too much complexity for their very few uses.
Fixes:
    framework failure for tc251(runTest) Unhandled exception:
    too many values to unpack

Before, the testsuite just printed
    Unhandled exception in thread started by <function test_common_thread at 0x188bde8>
    [...]
and carried on when using multiple threads, whereas it would just fall
over in single-threaded mode.

This fixes the testsuite driver with python 2.5. Patch from Florian Weimer.

Older versions of python, including that on the Windows nightly builder,
throw "SyntaxError: invalid syntax".

In particular, this allows more specific results to be specified, e.g.
    if_wordsize(64,                    stats_num_field('foo', 50, 54)),
    if_platform('x86_64-apple-darwin', stats_num_field('foo', 62, 66)),

This can make it a lot faster to run a single test.

You can run
    make CLEANUP=1 CLEAN_ONLY=YES
to clean everything without running any tests.