public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
To: Joseph Beckenbach <jbeckenbach@lancope.com>,
	"ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] More observations on HEAD
Date: Fri, 25 Jul 2014 12:03:25 +0400	[thread overview]
Message-ID: <53D20F4D.5000702@oracle.com> (raw)
In-Reply-To: <4506ACC2AE90484D87F9A883BA36C21C2ADF02C2@LCHQEX03.lancope.local>



On 07/19/2014 01:35 AM, Joseph Beckenbach wrote:
> Hi, all!

Hi!

>
> Feel free to ignore this -- it's an experience report of a cluster of runs I've just done against 3.12.24 kernels.
>
> The default test set runs move_pages* twice.
>
> setfsuid04_16 and setregid{02,04,05,07}_16 TFAIL rather than TCONF on no-16-bit-syscalls systems.

Hmm. Indeed, in my environment (OL6 + 3.8.13-26.2.3.el6uek.x86_64) 
setfsuid04_16 fails, but setregid{01,02,03,04}_16 don't. And there are 
no setregid{05, 07}_16

I'll look at setfsuid04_16.


>
> 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.
>
> dma_thread_diotest invocations all claim to be "dma_thread_diotest07" in the runltp outputfile.
>
> Thanks!
>
> Joseph
> Joseph Beckenbach, senior QA engineer : Automation
> x97166
> M 678-602-3192
>
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
>

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2014-07-25  8:03 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 [this message]
2014-07-25  8:51   ` Stanislav Kholmanskikh
2014-07-29 10:11     ` chrubis
2014-08-11 16:06 ` chrubis

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=53D20F4D.5000702@oracle.com \
    --to=stanislav.kholmanskikh@oracle.com \
    --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