Difference between revisions of "Test suite"
(→Known test suite issues) |
(→Software needed for running "make check": Update from "Building") |
||
| Line 10: | Line 10: | ||
* ''make install'' (as root, unless you gave a --prefix option to configure which you can write to as yourself) |
* ''make install'' (as root, unless you gave a --prefix option to configure which you can write to as yourself) |
||
| − | == |
+ | == Additional build requirements for running "make check" == |
| − | On Ubuntu or Debian systems, a number of packages need to be installed in order for "make check" to function. These include: |
||
| + | The following additional software (in addition to the requirements at [[Building]]) is needed to run "make check". As for [[Building]], the software packages are identified by their Debian / Ubuntu package names. |
||
| − | * dejagnu |
||
| + | * csh (for some of the Berkeley DB tests) |
||
| − | * expect |
||
| + | * dejagnu (for many dejagnu-based tests) |
||
| − | * tcl |
||
| + | * expect (needed by dejagnu) |
||
| − | * tcl-dev (needed by test programs that are extensions to the tcl program) |
||
| + | * g++ (for some API sanity checks) |
||
| − | * portmap ( |
+ | * portmap (for lib/rpc/unit-test) |
| − | * |
+ | * tcl (needed by expect) |
| − | * |
+ | * tcl-dev (to build some kadm5 test programs) |
| − | * ncurses-dev |
||
| − | * libtool libltd13-dev |
||
== Known test suite issues == |
== Known test suite issues == |
||
Revision as of 17:39, 27 June 2011
Procedure
- svn checkout svn://anonsvn.mit.edu/krb5/trunk
- Navigate to trunk/src
- util/reconf
- ./configure
- make
- make check
- make install (as root, unless you gave a --prefix option to configure which you can write to as yourself)
Additional build requirements for running "make check"
The following additional software (in addition to the requirements at Building) is needed to run "make check". As for Building, the software packages are identified by their Debian / Ubuntu package names.
- csh (for some of the Berkeley DB tests)
- dejagnu (for many dejagnu-based tests)
- expect (needed by dejagnu)
- g++ (for some API sanity checks)
- portmap (for lib/rpc/unit-test)
- tcl (needed by expect)
- tcl-dev (to build some kadm5 test programs)
Known test suite issues
On Linux systems, sometimes the --disable-rpath option to configure is required in order to avoid problems with previously-installed versions of MIT krb5. Alternatively, you can run "make install" before "make check".
Prior to krb5-1.9, calls to krb5_c_random_os_entropy that pass the value 1 in the strong argument (which causes the library to read from the strong OS random number source) can cause stalls and timeouts in the test suite. Changing those calls to pass 0 instead will reduce the stalls. Starting in krb5-1.9, we disable the reading of strong random numbers during tests. This is primarily a problem on Linux systems.
If an existing kdc.conf exists in the "installed" location, it can disrupt the automated tests, especially if it contains syntax errors.
On older Debian or Ubuntu systems, a bug in expect could cause stalls in the dejagnu parts of the test suite. It is documented at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421187. Current stable releases of Debian and Ubuntu no longer have an affected version of the expect package.
