Browse Source

fix some typos

master
George Danchev 11 years ago
parent
commit
7b3b12bfa1
  1. 17
      releng/README

17
releng/README

@ -46,7 +46,7 @@ There are two groups of test scripts:
These tests have a moderate resource consumption and do
not cause mechanical movements of drive trays.
manual_* get started by the user if desired.
manual_* gets started by the user if desired.
Manual tests may create larger sets of temporary files,
may download test data from the internet, may need
system privileges beyond the reach of a sandbox user,
@ -80,7 +80,7 @@ There are several options which work with run_all_auto and any single test.
-k keep self-generated data.
-c cleanup temporary data kept from previous run and exit.
-f simulate failure.
-h print this help text
-h print this help text.
-- end of general options, begin of test specific options.
After option "--", there may be given options which are specific to
particular manually executable test scripts.
@ -101,7 +101,7 @@ the user or require sysadmin considerations before they are run:
drives to examine more closely.
If a privilege command and optional arguments are given with --priv_cmd,
then this command and arguments are used to launch the xorriso runs.
Command and arguments must be single words and be submitted alltogether
Command and arguments must be single words and be submitted altogether
as one single argument. On Solaris use: --priv_cmd pfexec
./manual_burn -x ../xorriso/xorriso [-- [--dev device_file_to_use]
@ -116,14 +116,14 @@ the user or require sysadmin considerations before they are run:
state are reported but still regarded as success.
If a privilege command and optional arguments are given with --priv_cmd,
then this command and arguments are used to laynch the xorriso runs.
Command and arguments must be single words and be submitted alltogether
Command and arguments must be single words and be submitted altogether
as one single argument. On Solaris use: --priv_cmd pfexec
./manual_isojigdo -x ../xorriso/xorriso
Exercises the production of a bootable Debian GNU/Linux image and its Jigdo
files. This test downloads a Debian daily image for i386 of about 70 MB,
extracts its content and composes a new image. Thus it needs about 250 MB
of disk space in releng/releng_generated_data .
of disk space in releng/releng_generated_data.
This test will only work with GNU xorriso or if libjte was installed already
when libisofs was built. Further it needs the script jigdo-gen-md5-list
and the program jigit-mkimage. All three are part of package jigit,
@ -164,7 +164,7 @@ The text output of the automatic tests is recorded in file
releng_generated_data/log.run_all_auto
Script ./run_all_auto will detect failure of perticular tests and report
lines from the log file which contain problem indicating key words:
lines from the log file which contain problem indicating keywords:
NEVER,ABORT,FATAL,FAILURE,MISHAP,SORRY,WARNING,HINT,FAIL,ERROR,WRONG
If the program messages in log.run_all_auto do not explain the failure,
@ -202,7 +202,7 @@ for it
test_name="releng/manual_"...some.name...
or
test_name="releng/auto_"...some.name...
Then copy file releng/template_new to $test_name .
Then copy file releng/template_new to $test_name.
Edit $test_name and process any line that begins by "# === TEMPLATE:".
Do what the line prescribes and then remove it from the script. You are
not done as long as such a line remains.
@ -211,7 +211,8 @@ Your test must not start if no file
./inc/releng_getopts.inc
exists, i.e. if the current working directory is not ./releng.
If your test creates own files on disk, then it must do this underneath
directory ./releng_generated_data/$test_name (resp. $GEN_DATA_DIR, see below).
directory
./releng_generated_data/$test_name (resp. $GEN_DATA_DIR, see below).
In case of failure, issue a line to stdout that begins by the word "FAIL",
followed by " : " and the name of the test (e.g. $SELF, see below).

Loading…
Cancel
Save