mirrors/emacs
1
Fork 0
mirror of git://git.sv.gnu.org/emacs.git synced 2026-04-27 08:43:40 -07:00
Code Issues Projects Releases Wiki Activity
emacs/mps/test
History
Gareth Rees 8fc96e7609 Mmqa test harness improvements: 
* Don't compile for profiling (not needed at the moment)
* Compile with -Wno-unused -Wno-missing-prototypes on OS X (so that argerr/146.c and similar test cases will build).
* Output conclusion for the first failing result (in alphabetical order), rather than whatever comes out of the hash table first.
* Don't gather symbols from block comments, otherwise we can't specify results like "assertcond = mps_pool_o != NULL" as MMQA will think that mps_pool_o is a missing symbol.

Copied from Perforce
 Change: 187244
 ServerID: perforce.ravenbrook.com
2014-10-13 18:33:37 +01:00
..
argerr More test maintenance: 2013-05-25 11:35:44 +01:00
conerr More test maintenance: 2013-05-25 11:35:44 +01:00
function Turn off the spare memory on the mvff pool so that it returns freed memory to the arena immediately. 2014-10-11 00:57:28 +01:00
misc Long delayed maintenance of test suite: 2013-05-25 10:33:30 +01:00
test Mmqa test harness improvements: 2014-10-13 18:33:37 +01:00
testsets Turn off the spare memory on the mvff pool so that it returns freed memory to the arena immediately. 2014-10-11 00:57:28 +01:00
README It's better to run from test directory -- otherwise testsets will have to be rewritten. 2014-10-10 16:56:34 +01:00

README 

$Id$

This is the Memory Management QA test harness. To use it you need
perl 5 (or higher). Go "perl qa help" for help, "perl qa options"
to see what version of the harness you have (or look at the
file "test/version").


Testing on unix
---------------

From the test directory::

    $ PLATFORM=lii6ll # substitute your platform
    $ CODE=../code # code directory of the branch you are testing
    $ make -C $CODE -f $PLATFORM.gmk VARIETY=cool $PLATFORM/cool/mps.o
    $ alias qa="perl test/qa -i $CODE -l $CODE/$PLATFORM/cool/mps.o"
    $ qa clib
    $ qa run function/5.c
    $ qa runset testsets/passing

Each test case is compiled in its turn to the file
``test/obj/$(uname -s)_$(uname -r)_$(uname -p)__unix/tmp_test``
so you can debug it with::

    $ lldb test/obj/$(uname -s)_$(uname -r)_$(uname -p)__unix/tmp_test

(Or ``gdb`` instead of ``lldb``.)