Re: Feedback on LSB-FHS2.2beta test suite

[Andrew Josey <ajosey@rdg.opengroup.org>]

Candee
Many thanks for your feedback. Comments interspersed below:

On Jul 24,  4:49pm in "Feedback on LSB-FHS2", Candee Sumner wrote:
> Ran the tests on our MSC.Linux V2001 (June) distribution. Generally
> good, with the following comments.
>
> 1. I like the rerun_tests option. However, while initially running the
> setup.sh script it asks if you want to Build and Execute testsets, then
> immediately asks if you want to (Re)Build testsets. It's kind of
> confusing.
>
{bits deleted}

> 2. The message that is currently issued when the tests are not rebuilt
> but executed is
>
> Executing testsetstcc: journal file is
> /users/tet/test_sets/results/0005e/journal1
>
> It should be on two separate lines as follows.
>
> Executing testsets
> tcc: journal file is /users/tet/test_sets/results/0005e/journal1

Agreed. I have updated the module
test_sets/harness/vsxgen/run_testsets.sh
to make this clearer as you suggest

>
> 3. Looks like the rerun_tests option has problems identifying the test
> suite. I ran the script as the vsx0 user in its home directory
> (/users/tet/test_sets). I get the "(Re)Build testsets ..?" question  and
> then the following error.
>
> Executing testsetstcc (tcc.c, 355): can't determine test suite name
>
> It then produces the summary report and asks if I want to produce a
> journal of the failures.
>
> Nothing was re-executed, and when I answer the failure question, I get
> the following error.
>
> running tcc -p -e -s scen.exec -r FAIL,UNRESOLVED,UNINITIATED
> results/0003e/journal
> tcc (tcc.c, 355): can't determine test suite name
>
> Note that my TET_ROOT is /users/tet instead of /home/tet.
>
> The line
>
>  tcc -p -b -s $HOME/scen.bld $*
>
> in /users/tet/test_sets/run_testsets.sh produces the error. Ran manually
> with
>
> tcc -p -b -s $HOME/scen.bld test_sets
>
> and it ran fine.
>
> The following lines in the run_testsets.sh file do not find the test
> suite name.
>
> tcc -p -b -s $HOME/scen.bld $*
> tcc -p -e -s $HOME/scen.exec $*
> tcc -p -e -s scen.exec -r FAIL,UNRESOLVED,UNINITIATED
> results/$JNLDIR/journal

This may be caused by use of a symlink in the file tree which
can confuse tcc ? I will discuss this with folks here to work
out the best fix .

>
> 4. The following tests should also look to see if the test and [
> utilities are in the /usr/bin directory as this is valid according to
> the FHS 2.2 spec.
>
> Reference 3.1-49 (A)
> The implementation provides an exec-able version of the [
> utility in the /bin directory.
> Result: PASS/FAIL
> Note: this test is added for FHS2.2
>
> Reference 3.1-50 (A)
> The implementation provides an exec-able version of the test
> utility in the /bin directory.
> Result: PASS/FAIL
> Note: this test is added for FHS2.2
>
You are correct, I missed the "either case" . I will fix this.

regards
Andrew