File: run.html

package info (click to toggle)
evolution-data-server 1.0.4-1
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 39,504 kB
  • ctags: 26,423
  • sloc: ansic: 175,347; tcl: 30,499; sh: 20,699; perl: 11,320; xml: 9,039; java: 7,653; cpp: 6,029; makefile: 4,866; awk: 1,338; yacc: 1,103; sed: 772; cs: 505; lex: 134; asm: 14
file content (80 lines) | stat: -rw-r--r-- 4,196 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
<!--$Id: run.html,v 1.1.1.1 2003/11/20 22:14:21 toshok Exp $-->
<!--Copyright 1997-2002 by Sleepycat Software, Inc.-->
<!--All rights reserved.-->
<!--See the file LICENSE for redistribution information.-->
<html>
<head>
<title>Berkeley DB Reference Guide: Running the test suite</title>
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++">
</head>
<body bgcolor=white>
<a name="2"><!--meow--></a>
<table width="100%"><tr valign=top>
<td><h3><dl><dt>Berkeley DB Reference Guide:<dd>Test Suite</dl></h3></td>
<td align=right><a href="../../ref/upgrade.4.1/disk.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../reftoc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/test/faq.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
<p>
<h1 align=center>Running the test suite</h1>
<p>Once you have started tclsh and have loaded the test.tcl source file (see
<a href="../../ref/build_unix/test.html">Running the test suite under UNIX</a>
and <a href="../../ref/build_win/test.html">Running the test suite under
Windows</a> for more information), you are ready to run the test suite.  At
the tclsh prompt, to run the entire test suite, enter the following:
<p><blockquote><pre>% run_std</pre></blockquote>
<p>Running all the tests can take from several hours to a few days to
complete, depending on your hardware.  For this reason, the output from
this command is redirected to a file in the current directory named
<b>ALL.OUT</b>.  Periodically, a line will be written to the standard
output, indicating what test is being run.  When the test suite has
finished, a single message indicating that the test suite completed
successfully or that it failed will be written.  If the run failed, you
should review the file <b>ALL.OUT</b> to determine which tests failed.
Errors will appear in that file as output lines, beginning with the
string "FAIL".
<p>It is also possible to run specific tests or tests for a particular
subsystem:
<p><blockquote><pre>% r archive
% r btree
% r env
% r frecno
% r hash
% r join
% r join
% r lock
% r log
% r mpool
% r mutex
% r queue
% r rbtree
% r recno
% r rrecno
% r subdb
% r txn</pre></blockquote>
<p>Or to run a single, individual test:
<p><blockquote><pre>% test001 btree</pre></blockquote>
<p>It is also possible to modify the test run based on arguments on the
command line.  For example, the following command will run a greatly
abbreviated form of test001, doing 10 operations instead of 10,000:
<p><blockquote><pre>% test001 btree 10</pre></blockquote>
<p>In all cases, when not running the entire test suite as described
previously, a successful test run will return you to the tclsh prompt.
On failure, a message is displayed indicating what failed.
<p>Tests are run, by default, in the directory <b>TESTDIR</b>.  However,
the test files are often very large.  To use a different directory for
the test directory, edit the file include.tcl in your build directory,
and change the following line to a more appropriate value for your
system:
<p><blockquote><pre>set testdir ./TESTDIR</pre></blockquote>
<p>For example, you might change it to the following:
<p><blockquote><pre>set testdir /var/tmp/db.test</pre></blockquote>
<p>Alternatively, you can create a symbolic link named TESTDIR in your
build directory to an appropriate location for running the tests.
Regardless of where you run the tests, the TESTDIR directory should be
on a local filesystem, using a remote filesystem (for example, NFS) will
almost certainly cause spurious test failures.
<table width="100%"><tr><td><br></td><td align=right><a href="../../ref/upgrade.4.1/disk.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../reftoc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/test/faq.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
<p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font>
</body>
</html>