From: chrubis@suse.cz
To: Joseph Beckenbach <jbeckenbach@lancope.com>
Cc: "ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] More observations on HEAD
Date: Mon, 11 Aug 2014 18:06:49 +0200 [thread overview]
Message-ID: <20140811160648.GA5271@rei> (raw)
In-Reply-To: <4506ACC2AE90484D87F9A883BA36C21C2ADF02C2@LCHQEX03.lancope.local>
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
chrubis@suse.cz
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2014-08-11 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 21:35 [LTP] More observations on HEAD Joseph Beckenbach
2014-07-25 8:03 ` Stanislav Kholmanskikh
2014-07-25 8:51 ` Stanislav Kholmanskikh
2014-07-29 10:11 ` chrubis
2014-08-11 16:06 ` chrubis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140811160648.GA5271@rei \
--to=chrubis@suse.cz \
--cc=jbeckenbach@lancope.com \
--cc=ltp-list@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox