All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julio Cruz Barroso <julio.cruz@smartmatic.com>
To: ltp@lists.linux.it
Subject: [LTP] Question about perf_event_open/Cap_bounds/su01 test cases
Date: Wed, 9 Mar 2016 10:40:59 +0000	[thread overview]
Message-ID: <AF04265A3FC2B144B9892F621A394E13EA3DB009@tethys> (raw)

Hi,

I’m trying to perform a testing based on LTP version 20150420 on a Linux 3.14.61 (using iMX6 SOC series).

Basically, I perform the same test in four (4) different SOC (Solo, DualLite, Dual and Quad) including different RAM (512, 512, 1024, 2048MB respectively). The same kernel (with different Device Tree) is used on the four boards.

The test is run as below:

------------------
hostname emad-machine ; 
cd /opt/ltp ; 
rm -r tmp ; 
mkdir tmp ; 
chmod 777 tmp ; 
rm -r results ; 
rm result.fulllog ; 
rm -r output ; 
./runltp -p -l result.log -C result.fail -d /opt/ltp/tmp -g results.html -o result.fulllog
------------------

The results show around 66 test cases fail from a total of 1519. I focused on the fails trying to:

------------------
1) Change the kernel configuration (rebuild) to include any missing option
2) Review the test cases code and try to figure out any false negative
------------------

After perform this analysis, 63 test cases were mark as false negatives, but 4 test cases have unknown conclusion, as show below:

------------------
1. perf_event_open01 failed with < TEST_ERRNO=EOPNOTSUPP(95): Operation not supported. >
   a. I assume the test fail because the HW doesn’t support it. Could be wrong? [more details, please refer to https://justpaste.it/s315]
2. perf_event_open02 cause < WARNING: CPU: 2 PID: 24@kernel/events/core.c:764 perf_cpu_hrtimer_handler+0x1f0/0x20c() >. This warning pass multiples times until /dev/kmsg buffer overrun [more details, please refer to https://justpaste.it/s315]
   a. This test fail because the 01 test already fail, or can I run both independently?
   b. Any advice about the WARNING?  
3. Cap_bounds fail with “cap_bounds_r.c:55: prctl(PR_CAPBSET_READ, 37) returned -1”. The numerical value of the highest capability supported by the running kernel is 36 [cat /proc/sys/kernel/cap_last_cap, http://man7.org/linux/man-pages/man7/capabilities.7.html]. 
   a. Can I assume this as a false negative?
4. su01 fail with < /bin/su -l root with correct password ( FAILED ) > [more details, please refer to https://justpaste.it/s329]. 
   a. Could be an test issue?
------------------

The whole analysis can be refer on https://justpaste.it/s32h. 

Appreciate any suggestion or feedback. I just started using LTP some days ago, please, forgive any huge mistake ☺

Thanks, Julio




             reply	other threads:[~2016-03-09 10:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 10:40 Julio Cruz Barroso [this message]
2016-03-09 12:08 ` [LTP] Question about perf_event_open/Cap_bounds/su01 test cases Jan Stancek
2016-03-09 13:52   ` Cyril Hrubis
2016-03-09 14:08 ` Cyril Hrubis
2016-03-11 13:35   ` Julio Cruz Barroso
2016-03-11 15:35     ` Jan Stancek
2016-03-12 12:01       ` Julio Cruz Barroso
2016-03-12 13:45         ` Jan Stancek
2016-03-13 11:39           ` Julio Cruz Barroso
2016-03-14 12:10             ` Jan Stancek
2016-03-15 10:35               ` Julio Cruz Barroso
2016-03-14 18:18     ` Cyril Hrubis
2016-03-15 15:07       ` Cyril Hrubis

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=AF04265A3FC2B144B9892F621A394E13EA3DB009@tethys \
    --to=julio.cruz@smartmatic.com \
    --cc=ltp@lists.linux.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.