On 11/05/2012 08:29 PM, Joseph Rushton Wakeling wrote:
> Once pulled in, how do I go about running the unittests on all code (DFE,
> druntime, phobos) as part of the build process?  (Something worth adding to GDC
> wiki perhaps?)

Whoops, there I go jumping ahead of myself: http://www.gdcproject.org/wiki/Test%20suite

I redid a build with --enable-checking=yes; there are a number of "unexpected" failures, and make exits with an error.  I also don't see any indication that the Phobos unittests were run.

This is just vanilla gdc-4.7, I have not yet pulled in any patches for 2.060.

--------------------------------------------------------------------------------
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /home/joseph/code/D/gdc-4.7/gcc-4.7-4.7.2/src/gcc/testsuite/config/default.exp as tool-and-target-specific interface file.
Running /home/joseph/code/D/gdc-4.7/gcc-4.7-4.7.2/src/gcc/testsuite/gdc.test/d_do_test.exp ...
FAIL: compilable/ddoc12.d output-exists ddoc12.o
FAIL: compilable/interpret3.d output-exists interpret3.o
FAIL: compilable/line.d output-exists line.o
FAIL: compilable/test7190.d output-exists test7190.o
FAIL: fail_compilation/fail129.d output-exists-not fail129.s
FAIL: fail_compilation/fail308.d output-exists-not fail308.s
FAIL: fail_compilation/fail6451.d output-exists-not fail6451.s
FAIL: runnable/bench1.d execution test
FAIL: runnable/deprecate1.d (internal compiler error)
FAIL: runnable/pi.d execution test
FAIL: runnable/printargs.d execution test
FAIL: runnable/test15.d execution test
FAIL: runnable/test19.d execution test
FAIL: runnable/test4.d execution test
FAIL: runnable/test41.d execution test
FAIL: runnable/testformat.d execution test
FAIL: runnable/teststdio.d execution test
FAIL: runnable/testzip.d execution test
FAIL: runnable/version.d execution test
FAIL: runnable/xtest46.d execution test

		=== gdc Summary ===

# of expected passes		1290
# of unexpected failures	20
# of unresolved testcases	15
/home/joseph/code/D/gdc-4.7/objdir/gcc/testsuite/gdc/../../gdc  version 4.7.2 (Linaro GCC 4.7-2012.09-1~dev)

make[2]: [check-parallel-gdc] Error 1 (ignored)
--------------------------------------------------------------------------------

Am Mon, 05 Nov 2012 20:53:57 +0100
schrieb Joseph Rushton Wakeling <joseph.wakeling@webdrake.net>:

> On 11/05/2012 08:29 PM, Joseph Rushton Wakeling wrote:
> > Once pulled in, how do I go about running the unittests on all code
> > (DFE, druntime, phobos) as part of the build process?  (Something
> > worth adding to GDC wiki perhaps?)
> 
> Whoops, there I go jumping ahead of myself: http://www.gdcproject.org/wiki/Test%20suite
> 
> I redid a build with --enable-checking=yes; there are a number of "unexpected" failures, and make exits with an error.  I also don't see any indication that the Phobos unittests were run.
> 
> This is just vanilla gdc-4.7, I have not yet pulled in any patches for 2.060.
> 

We currently do not run the pbobos / druntime unittests. There's a "unittest" target in the Makefile, so it's possible to use "make unittest" in the phobos/druntime directory, but the Makefile is outdated and won't work.

We really need to properly integrate the unittests, but for now running phobos tests is not supported.

The "unexpected" failures are kinda expected ;-) The dmd testsuite hasn't been ported 100% to the gcc testsuite so some tests fail because they can't find some extra files or because of similar errors. Some failures are probably real problems though.

Anyway, don't expect all tests to pass for now. Just use the test suite for regression testing when merging a new frontend.