Hi!
> The default test set runs move_pages* twice.

True, these are part of two different runtest files and both runtest
files are part of default scenario. I do not think that this is wrong as
it is.

It's rather limitation of the current system to run testcases. What I
would rather is is some label based system, where testcases can be
labeled with different scenarios.

I.e. in this cases move_pages would be labeled as syscalls, numa and
default. Then we can run testcases by labels rather than runtest
files...

> run_cgroup_test_fj.sh hangs on heavy-load systems with $LTPROOT/output/ not 
> present.
> 
> Some test under container_test.sh (sourcing childns.sh) attempts to create 
> veth pairs without verifying veth functionality supported.
> Other tests under container_test.sh fail to source files (childns.sh cannot 
> source cmdlib.sh;  child_1.sh and childipv6.sh cannot source initialize.sh).
> 
> Many tests under cgroup_regression_test.sh blindly log to hard-coded 
> $LTPROOT/output/ directory without making sure it's there.
> Also, subtest #7 "fails to mount hugetlb" because it seemingly did not first 
> check whether the functionality was enabled.
> 
> Under cgroup_fj also seems to have some tests which do latency tests and 
> other tests, outputting "TINFO" and "FAIL" and "PASS" not in standard format.
> I will see if I can bisect it down and work out which tests those are.

Adding checks for missing functionality should be pretty
straightforward and patches are welcome :).

The runltp script contains code to create the $LTPROOT/output directory
so there are a few testcases that expect that directory to exist,
nevertheless they should create test temporary directory with tst_tmpdir
and use it instead.

> dma_thread_diotest invocations all claim to be "dma_thread_diotest07" in the 
> runltp outputfile.

We forget to rename the TCID after we renamed the file. Fixed.

-- 
Cyril Hrubis
chru...@suse.cz

------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Reply via email to