Commit graph

4 commits

Author SHA1 Message Date
thorpej
472857adc0 Bump to 1.4.3nb2, apply this patch from the dejagnu on
gcc.gnu.org:

2003-06-13  Jason Thorpe  <thorpej@wasabisystems.com>

	* lib/target.exp (prune_warnings): Add two more linker
	warning patterns for warnings generated by modern verions
	of NetBSD.
2003-06-14 00:24:27 +00:00
kristerw
26edb42e36 Update dejagnu to 1.4.3nb1.
Fix bug that made tests organized in deep directory structures (e.g. the
gcc testsuite) be run multiple times.
2002-11-25 21:13:51 +00:00
kristerw
60e6a01753 Update devel/dejagnu to version 1.4.3.
Changes since 1.4.1 include:
- New XML output option, so test results can be loaded into a database.
- Support for the KFAIL/KPASS (known failures). This is mostly oriented
  towards GDB testing.
- New tutorial chapter.
- Test case builds with either libstdc++-v3 (as used by gcc-3.0.x) or the
  older v2.(as used by gcc-2.95.x)
2002-09-27 23:43:42 +00:00
tv
beb5a2646d DejaGnu is a framework for testing other programs. Its purpose is to
provide a single front end for all tests.  Beyond this, DejaGnu offers
several advantages for testing:

        - The flexibility and consistency of the DejaGnu framework
          make it easy to write tests for any program.

        - DejaGnu provides a layer of abstraction which makes all
          tests (if correctly written) portable to any host or target
          where a program must be tested.  For instance, a test for
          GDB can run (from any Unix based host) on any target
          architecture supported by DejaGnu. Currently DejaGnu runs
          tests on several single board computers, whose operating
          software ranges from just a boot monitor to a full-fledged,
          Unix-like realtime OS.

        - DejaGnu is written in expect, which in turn uses Tcl
          (Tool command language).  The framework comprises two parts:
          the testing framework and the testsuites themselves. Tests
          are usually written in expect using Tcl.
2001-05-30 04:17:52 +00:00