Acceptance Small (acc-sm) Testing on Lustre - Revision history

Sbarthel: /* Do you have to run every acc-sm test? */

2010-03-10T17:46:09Z

Do you have to run every acc-sm test?

← Older revision		Revision as of 10:46, 10 March 2010
Line 191:		Line 191:
	ACC_SM_ONLY=SANITY STOP_AT=77j sh acceptance-small.sh		ACC_SM_ONLY=SANITY STOP_AT=77j sh acceptance-small.sh

	To start and stop the test suite ~~within~~ a ~~defined~~ range of tests, use START_AT and STOP_AT. For example, to run sanity tests from 23b to 24f:		To start and stop the test suite to define a range of tests, use START_AT and STOP_AT. For example, to run sanity tests from 23b to 24f:

	ACC_SM_ONLY=SANITY START_AT=23b STOP_AT=24f sh acceptance-small.sh		ACC_SM_ONLY=SANITY START_AT=23b STOP_AT=24f sh acceptance-small.sh

Sbarthel: /* Do you have to run every acc-sm test? */

2010-03-10T17:44:07Z

Do you have to run every acc-sm test?

← Older revision		Revision as of 10:44, 10 March 2010
Line 161:		Line 161:
	==Do you have to run every acc-sm test?==		==Do you have to run every acc-sm test?==

	No. You can choose to run only specified acc-sm tests or start the test suite from a defined test. Tests can be run either with or without the acceptance-sm.sh (acc-sm.sh) wrapper script. Here are several examples:		No. You can choose to run only specified acc-sm tests, start the test suite from a defined test, or stop the test suite at a defined test. Tests can be run either with or without the acceptance-sm.sh (acc-sm.sh) wrapper script. Here are several examples:

	To only run the RUNTESTS and SANITY tests:		To only run the RUNTESTS and SANITY tests:
Line 187:		Line 187:
	ACC_SM_ONLY=SANITY START_AT=24c sh acceptance-small.sh		ACC_SM_ONLY=SANITY START_AT=24c sh acceptance-small.sh

	To stop the test suite ~~from~~ a defined test, use STOP_AT. For example, to run sanity tests from 23b to 24f:		To stop the test suite at a defined test, use STOP_AT. For example:

			ACC_SM_ONLY=SANITY STOP_AT=77j sh acceptance-small.sh

			To start and stop the test suite within a defined range of tests, use START_AT and STOP_AT. For example, to run sanity tests from 23b to 24f:

	ACC_SM_ONLY=SANITY START_AT=23b STOP_AT=24f sh acceptance-small.sh		ACC_SM_ONLY=SANITY START_AT=23b STOP_AT=24f sh acceptance-small.sh

Sbarthel: /* Do you have to run every acc-sm test? */

2010-03-10T16:39:03Z

Do you have to run every acc-sm test?

← Older revision		Revision as of 09:39, 10 March 2010
Line 161:		Line 161:
	==Do you have to run every acc-sm test?==		==Do you have to run every acc-sm test?==

	No. You can choose to run only specified acc-sm tests. Tests can be run either with or without the acceptance-sm.sh (acc-sm.sh) wrapper script. Here are several examples:		No. You can choose to run only specified acc-sm tests or start the test suite from a defined test. Tests can be run either with or without the acceptance-sm.sh (acc-sm.sh) wrapper script. Here are several examples:

	To only run the RUNTESTS and SANITY tests:		To only run the RUNTESTS and SANITY tests:
Line 178:		Line 178:

	CONF_SANITY_EXCEPT=”$(seq 15)“ sh conf-sanity.sh		CONF_SANITY_EXCEPT=”$(seq 15)“ sh conf-sanity.sh

			To start the test suite from a defined test, use START_AT. For example:

			ACC_SM_ONLY=SANITY_BENCHMARK START_AT=fsx sh acceptance-small.sh

			-or-

			ACC_SM_ONLY=SANITY START_AT=24c sh acceptance-small.sh

			To stop the test suite from a defined test, use STOP_AT. For example, to run sanity tests from 23b to 24f:

			ACC_SM_ONLY=SANITY START_AT=23b STOP_AT=24f sh acceptance-small.sh

	==Do the acc-sm tests have to be run in a specific order?==		==Do the acc-sm tests have to be run in a specific order?==

Sbarthel at 13:12, 22 February 2010

2010-02-22T13:12:20Z

← Older revision		Revision as of 06:12, 22 February 2010
Line 1:		Line 1:
	<small>''(Updated: Feb 2010)''</small>		<small>''(Updated: Feb 2010)''</small>
	__TOC__		__TOC__

	The Lustre™ QE group and developers use acceptance-small (acc-sm) tests to catch bugs early in the development cycle. Within the Lustre group, acc-sm tests are run on YALA, an automated test system. This information is being published to describe the steps to perform acceptance small testing and encourage wider acc-sm testing in the Lustre community.		The Lustre™ QE group and developers use acceptance-small (acc-sm) tests to catch bugs early in the development cycle. Within the Lustre group, acc-sm tests are run on YALA, an automated test system. This information is being published to describe the steps to perform acceptance small testing and encourage wider acc-sm testing in the Lustre community.

Sbarthel at 13:12, 22 February 2010

2010-02-22T13:12:03Z

← Older revision		Revision as of 06:12, 22 February 2010
Line 1:		Line 1:
	<small>''(Updated: Feb 2010)''</small>		<small>''(Updated: Feb 2010)''</small>

	__TOC__		__TOC__

Sbarthel at 13:11, 22 February 2010

2010-02-22T13:11:48Z

← Older revision		Revision as of 06:11, 22 February 2010
Line 1:		Line 1:
			<small>''(Updated: Feb 2010)''</small>

	__TOC__		__TOC__
	~~''(Updated: Feb 2010)''~~

	The Lustre™ QE group and developers use acceptance-small (acc-sm) tests to catch bugs early in the development cycle. Within the Lustre group, acc-sm tests are run on YALA, an automated test system. This information is being published to describe the steps to perform acceptance small testing and encourage wider acc-sm testing in the Lustre community.		The Lustre™ QE group and developers use acceptance-small (acc-sm) tests to catch bugs early in the development cycle. Within the Lustre group, acc-sm tests are run on YALA, an automated test system. This information is being published to describe the steps to perform acceptance small testing and encourage wider acc-sm testing in the Lustre community.

Sbarthel: /* What is the LOAD_MODULES_REMOTE variable and how is it used with acc-sm? */

2010-02-21T19:08:59Z

What is the LOAD_MODULES_REMOTE variable and how is it used with acc-sm?

← Older revision		Revision as of 12:08, 21 February 2010
Line 324:		Line 324:
	The LOAD_MODULES_REMOTE variable is used to load/unload modules on remote nodes.		The LOAD_MODULES_REMOTE variable is used to load/unload modules on remote nodes.

	*By default, LOAD_MODULES_REMOTE is "false" (LOAD_MODULES_REMOTE=false), and modules are not loaded or unloaded on remote nodes during acceptance small testing.		*By default, LOAD_MODULES_REMOTE is set to "false" (LOAD_MODULES_REMOTE=false), and modules are not loaded or unloaded on remote nodes during acceptance small testing.

	*If LOAD_MODULES_REMOTE is "true" (LOAD_MODULES_REMOTE=true), then modules are loaded/unloaded on remote nodes when running the acc-sm tests:		*If LOAD_MODULES_REMOTE is set to "true" (LOAD_MODULES_REMOTE=true), then modules are loaded/unloaded on remote nodes when running the acc-sm tests:

	LOAD_MODULES_REMOTE=true sh acceptance-small.sh		LOAD_MODULES_REMOTE=true sh acceptance-small.sh

Sbarthel: /* What is the FAILURE_MODE variable and how is it used with acc-sm? */

2010-02-21T19:08:01Z

What is the FAILURE_MODE variable and how is it used with acc-sm?

← Older revision		Revision as of 12:08, 21 February 2010
Line 457:		Line 457:
	The FAILURE_MODE variable is used to set the mode in which acc-sm emulates facet failure.		The FAILURE_MODE variable is used to set the mode in which acc-sm emulates facet failure.

	*By default, FAILURE_MODE is set to SOFT, which causes acc-sm to perform umount -f facet.		*By default, FAILURE_MODE is set to "SOFT" (FAILURE_MODE=SOFT), which causes acc-sm to perform umount -f facet.

	*If FAILURE_MODE is set to HARD, then acc-sm runs the functions specified by the following variables:		*If FAILURE_MODE is set to "HARD" (FAILURE_MODE=HARD), then acc-sm runs the functions specified by the following variables:

	POWER_DOWN=${POWER_DOWN:-"powerman --off"}		POWER_DOWN=${POWER_DOWN:-"powerman --off"}

Sbarthel: /* What is the FAILURE_MODE variable and how is it used with acc-sm? */

2010-02-21T19:05:52Z

What is the FAILURE_MODE variable and how is it used with acc-sm?

← Older revision		Revision as of 12:05, 21 February 2010
Line 455:		Line 455:
	==What is the FAILURE_MODE variable and how is it used with acc-sm?==		==What is the FAILURE_MODE variable and how is it used with acc-sm?==

	The FAILURE_MODE variable is used to set the mode in which acc-sm emulates facet failure. By default, FAILURE_MODE is set to SOFT, which causes acc-sm to perform umount -f facet. If FAILURE_MODE is set to HARD, then acc-sm runs the functions specified by the following variables:		The FAILURE_MODE variable is used to set the mode in which acc-sm emulates facet failure.

			*By default, FAILURE_MODE is set to SOFT, which causes acc-sm to perform umount -f facet.

			*If FAILURE_MODE is set to HARD, then acc-sm runs the functions specified by the following variables:

	POWER_DOWN=${POWER_DOWN:-"powerman --off"}		POWER_DOWN=${POWER_DOWN:-"powerman --off"}

Sbarthel: /* What is the SHARED_DIRECTORY variable and how is it used with acc-sm? */

2010-02-21T19:03:14Z

What is the SHARED_DIRECTORY variable and how is it used with acc-sm?

← Older revision		Revision as of 12:03, 21 February 2010
Line 433:		Line 433:
	By default, SHARED_DIRECTORY is empty; it has no default value.		By default, SHARED_DIRECTORY is empty; it has no default value.

	~~The~~ SHARED_DIRECTORY variable must be set to a reasonable value; otherwise, the above-listed test suites will fail.		SHARED_DIRECTORY variable must be set to a reasonable value; otherwise, the above-listed test suites will fail.

	To specify ~~the~~ SHARED_DIRECTORY ~~parameter~~, set the following in your test environment:		To specify SHARED_DIRECTORY, set the following in your test environment:

	SHARED_DIRECTORY=/path/to/shared/dir		SHARED_DIRECTORY=/path/to/shared/dir