Test suite - Revision history

Sarah at 14:47, 8 December 2015

2015-12-08T14:47:06Z

Ghudson at 16:27, 4 December 2015

2015-12-04T16:27:10Z

Ghudson at 17:11, 7 June 2014

2014-06-07T17:11:39Z

BenKaduk: reverse-resolution test suite issues

2012-07-03T19:59:49Z

reverse-resolution test suite issues

TomYu: /* Known test suite issues */

2011-06-28T23:07:04Z

‎Known test suite issues

TomYu: /* Known test suite issues */ Dejagnu breaks Tcl autoloading

2011-06-28T20:54:09Z

‎Known test suite issues: Dejagnu breaks Tcl autoloading

TomYu at 22:51, 27 June 2011

2011-06-27T22:51:21Z

TomYu: Delete "Procedure", as it duplicated stuff at "Building". Minor style changes.

2011-06-27T22:45:30Z

Delete "Procedure", as it duplicated stuff at "Building". Minor style changes.

TomYu: /* Software needed for running "make check" */ Update from "Building"

2011-06-27T22:39:34Z

‎Software needed for running "make check": Update from "Building"

TomYu: /* Known test suite issues */

2011-06-27T22:35:29Z

‎Known test suite issues

← Older revision		Revision as of 14:47, 8 December 2015
Line 32:		Line 32:

	As of December 2015, on Fedora Linux, portions of the test suite will fail if the current hostname is not all lower-case and is not registered in the DNS. Our hostname canonicalization procedure (krb5_sname_to_principal()) downcases the result as the last step. Fedora uses nss-myhostname to ensure that the local hostname resolves, and (for reasons we're not completely certain of) nss-myhostname does not appear to work with a different case from the canonical one.		As of December 2015, on Fedora Linux, portions of the test suite will fail if the current hostname is not all lower-case and is not registered in the DNS. Our hostname canonicalization procedure (krb5_sname_to_principal()) downcases the result as the last step. Fedora uses nss-myhostname to ensure that the local hostname resolves, and (for reasons we're not completely certain of) nss-myhostname does not appear to work with a different case from the canonical one.
		+
		+	As of December 2015, running the test suite using the make flag -j9 causes the tests to fail, specifically in the kadm5 unit-test. There seems to be some issues with the test suite and parallel processing. For now make sure to run everything in sequence.

@@ Line 13: / Line 13: @@
 == Known test suite issues ==
-On Linux systems, sometimes the <code>--disable-rpath</code> option to <code>configure</code> 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, on Linux systems, sometimes the <code>--disable-rpath</code> option to <code>configure</code> 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 <code>strong</code> 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.
@@ Line 30: / Line 30: @@
 As of July 2012, portions of the test suite will fail if the current hostname does not properly resolve (e.g., if a hostname is set, but the IP address assigned via DHCP corresponds to a different name); setting explicit entries in <code>/etc/hosts</code> should be an effective workaround (an IPv6 entry may be needed in addition to an IPv4 entry).

@@ Line 8: / Line 8: @@
 * expect (needed by dejagnu)
 * g++ (for some API sanity checks)
 * tcl (needed by expect)
 * tcl-dev (to build some kadm5 test programs)

← Older revision		Revision as of 19:59, 3 July 2012
Line 29:		Line 29:

	On older Debian or Ubuntu systems, a bug in <code>expect</code> 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 <code>expect</code> package.		On older Debian or Ubuntu systems, a bug in <code>expect</code> 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 <code>expect</code> package.
		+
		+	As of July 2012, portions of the test suite will fail if the current hostname does not properly resolve (e.g., if a hostname is set, but the IP address assigned via DHCP corresponds to a different name); setting explicit entries in <code>/etc/hosts</code> should be an effective workaround (an IPv6 entry may be needed in addition to an IPv4 entry).

@@ Line 24: / Line 24: @@
 </pre>
-The Dejagnu maintainers are aware of this problem (http://lists.gnu.org/archive/html/dejagnu/2011-03/msg00002.html), but as of June 2011 there doesn't seem to be a release containing the fix.  Since krb5-1.9, the offending piece of Tcl code (<code>clock format [clock seconds]</code>) is no longer used.
+The Dejagnu maintainers are aware of this problem (http://lists.gnu.org/archive/html/dejagnu/2011-03/msg00002.html), but as of June 2011 there doesn't seem to be a release containing the fix.  Since krb5-1.9, the offending piece of Tcl code (<code>clock format [clock seconds]</code>) is no longer used. A fix has been applied to the krb5-1.8 branch as well. ({{bug|6926}})
 If an existing kdc.conf exists in the "installed" location, it can disrupt the automated tests, especially if it contains syntax errors.

← Older revision		Revision as of 20:54, 28 June 2011
Line 17:		Line 17:

	Prior to krb5-1.9, calls to krb5_c_random_os_entropy that pass the value 1 in the <code>strong</code> 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.		Prior to krb5-1.9, calls to krb5_c_random_os_entropy that pass the value 1 in the <code>strong</code> 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.
		+
		+	Prior to krb5-1.9, the test suite tripped a bug where Dejagnu breaks the autoloading required by modern versions of Tcl. This manifests as errors such as:
		+
		+	<pre>
		+	ERROR: (DejaGnu) proc "::tcl::tm::UnknownHandler ::tclPkgUnknown msgcat 1.4" does not exist.
		+	</pre>
		+
		+	The Dejagnu maintainers are aware of this problem (http://lists.gnu.org/archive/html/dejagnu/2011-03/msg00002.html), but as of June 2011 there doesn't seem to be a release containing the fix. Since krb5-1.9, the offending piece of Tcl code (<code>clock format [clock seconds]</code>) is no longer used.

	If an existing kdc.conf exists in the "installed" location, it can disrupt the automated tests, especially if it contains syntax errors.		If an existing kdc.conf exists in the "installed" location, it can disrupt the automated tests, especially if it contains syntax errors.

← Older revision		Revision as of 22:51, 27 June 2011
Line 1:		Line 1:
	[[Category:Lore]]		[[Category:Lore]]
−
	== Additional build requirements for running "make check" ==		== Additional build requirements for running "make check" ==

@@ Line 1: / Line 1: @@
 [[Category:Lore]]
 == 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.
+The following additional software (in addition to the requirements at [[Building]]) is needed to run "make check".  As for the packages listed at [[Building]], the software packages are identified by their Debian / Ubuntu package names.
 * csh (for some of the Berkeley DB tests)

@@ Line 10: / Line 10: @@
 * ''make install'' (as root, unless you gave a --prefix option to configure which you can write to as yourself)
-== Software needed for running "make check" ==
+== Additional build requirements for running "make check" ==
-* portmap (needed by lib/rpc-unit-test)
+* portmap (for lib/rpc/unit-test)
-* g++
+* tcl (needed by expect)
-* byacc or bison (bison if you configure with "--enable-maintainer-mode" and need to rebuild certain of the parsers where we check in the generated C files)
+* tcl-dev (to build some kadm5 test programs)
 == Known test suite issues ==

@@ Line 28: / Line 28: @@
 On Linux systems, sometimes the <code>--disable-rpath</code> option to <code>configure</code> is required in order to avoid problems with previously-installed versions of MIT krb5.  Alternatively, you can run "make install" before "make check".
-The calls to krb5_c_random_os_entropy that pass the value 1 in the <code>strong</code> 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.  We need to have a better way to disable the reading of strong random numbers during tests.  This is primarily a problem on Linux systems.
+Prior to krb5-1.9, calls to krb5_c_random_os_entropy that pass the value 1 in the <code>strong</code> 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 recent Debian or Ubuntu systems, a bug in <code>expect</code> that can cause stalls in the dejagnu parts of the test suite is documented at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421187
+On older Debian or Ubuntu systems, a bug in <code>expect</code> 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 <code>expect</code> package.