All of lore.kernel.org
 help / color / mirror / Atom feed
* [LTP] ❌ FAIL: Test report for kernel 5.4.0-rc6-dd89262.cki (mainline.kernel.org)
@ 2019-11-11  8:05 CKI Project
  2019-11-11 17:00 ` Jan Stancek
  0 siblings, 1 reply; 4+ messages in thread
From: CKI Project @ 2019-11-11  8:05 UTC (permalink / raw)
  To: ltp


Hello,

We ran automated tests on a recent commit from this kernel tree:

       Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
            Commit: dd892625d0e2 - Merge tag 'staging-5.4-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging

The results of these automated tests are provided below.

    Overall result: FAILED (see details below)
             Merge: OK
           Compile: OK
             Tests: FAILED

All kernel binaries, config files, and logs are available for download here:

  https://artifacts.cki-project.org/pipelines/277487

One or more kernel tests failed:

    x86_64:
     ? selinux-policy: serge-testsuite
     ? LTP lite

We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.

Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.

        ,-.   ,-.
       ( C ) ( K )  Continuous
        `-',-.`-'   Kernel
          ( I )     Integration
           `-'
______________________________________________________________________________

Compile testing
---------------

We compiled the kernel for 1 architecture:

    x86_64:
      make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg


Hardware testing
----------------
We booted each kernel and ran the following tests:

  x86_64:
    Host 1:

       ? Internal infrastructure issues prevented one or more tests (marked
       with ???) from running on this architecture.
       This is not the fault of the kernel that was tested.

       ? Boot test
       ? xfstests: ext4
       ? xfstests: xfs
       ? selinux-policy: serge-testsuite
       ? lvm thinp sanity
       ? storage: software RAID testing
       ? ? IOMMU boot test
       ? ??? Storage blktests

    Host 2:
       ? Boot test
       ? ? IPMI driver test
       ? ? IPMItool loop stress test

    Host 3:
       ? Boot test
       ? Podman system integration test (as root)
       ? Podman system integration test (as user)
       ? LTP lite
       ? Loopdev Sanity
       ? jvm test suite
       ? Memory function: memfd_create
       ? Memory function: kaslr
       ? AMTU (Abstract Machine Test Utility)
       ? LTP: openposix test suite
       ? Networking bridge: sanity
       ? Ethernet drivers sanity
       ? Networking MACsec: sanity
       ? Networking socket: fuzz
       ? Networking sctp-auth: sockopts test
       ? Networking: igmp conformance test
       ? Networking route: pmtu
       ? Networking route_func: local
       ? Networking route_func: forward
       ? Networking TCP: keepalive test
       ? Networking UDP: socket
       ? Networking tunnel: geneve basic test
       ? Networking tunnel: gre basic
       ? L2TP basic test
       ? Networking tunnel: vxlan basic
       ? Networking ipsec: basic netns transport
       ? Networking ipsec: basic netns tunnel
       ? audit: audit testsuite test
       ? httpd: mod_ssl smoke sanity
       ? iotop: sanity
       ? tuned: tune-processes-through-perf
       ? pciutils: sanity smoke test
       ? ALSA PCM loopback test
       ? ALSA Control (mixer) Userspace Element test
       ? Usex - version 1.9-29
       ? storage: SCSI VPD
       ? stress: stress-ng
       ? trace: ftrace/tracer
       ? ? CIFS Connectathon
       ? ? POSIX pjd-fstest suites
       ? ? Networking vnic: ipvlan/basic
       ? ? storage: dm/common

  Test sources: https://github.com/CKI-project/tests-beaker
    ? Pull requests are welcome for new tests or improvements to existing tests!

Waived tests
------------
If the test run included waived tests, they are marked with ?. Such tests are
executed but their results are not taken into account. Tests are waived when
their results are not reliable enough, e.g. when they're just introduced or are
being fixed.

Testing timeout
---------------
We aim to provide a report within reasonable timeframe. Tests that haven't
finished running are marked with ?. Reports for non-upstream kernels have
a Beaker recipe linked to next to each host.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [LTP]  ❌ FAIL: Test report for kernel 5.4.0-rc6-dd89262.cki (mainline.kernel.org)
  2019-11-11  8:05 [LTP] ❌ FAIL: Test report for kernel 5.4.0-rc6-dd89262.cki (mainline.kernel.org) CKI Project
@ 2019-11-11 17:00 ` Jan Stancek
  2019-11-12  9:56   ` Jan Stancek
  0 siblings, 1 reply; 4+ messages in thread
From: Jan Stancek @ 2019-11-11 17:00 UTC (permalink / raw)
  To: ltp


----- Original Message -----
>      ? LTP lite

perf_event_open02 again:

<<<test_start>>>
tag=perf_event_open02 stime=1573434398
cmdline="perf_event_open02"
contacts=""
analysis=exit
<<<test_output>>>
perf_event_open02    0  TINFO  :  overall task clock: 54172980
perf_event_open02    0  TINFO  :  hw sum: 1423341410, task clock sum: 255289913
perf_event_open02    0  TINFO  :  ratio: 4.712495
perf_event_open02    1  TFAIL  :  perf_event_open02.c:394: test failed (ratio was greater than )
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=17 cstime=0
<<<test_end>>>

I ran it by hand on same system with same kernel. It's giving ratio close to 9
for past couple hours:

perf_event_open02    0  TINFO  :  overall task clock: 32829317
perf_event_open02    0  TINFO  :  hw sum: 2701673973, task clock sum: 295085628
perf_event_open02    0  TINFO  :  ratio: 8.988479
perf_event_open02    1  TPASS  :  test passed


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [LTP]  ❌ FAIL: Test report for kernel 5.4.0-rc6-dd89262.cki (mainline.kernel.org)
  2019-11-11 17:00 ` Jan Stancek
@ 2019-11-12  9:56   ` Jan Stancek
  2019-11-15  9:52     ` [LTP] ??? " Cyril Hrubis
  0 siblings, 1 reply; 4+ messages in thread
From: Jan Stancek @ 2019-11-12  9:56 UTC (permalink / raw)
  To: ltp



----- Original Message -----
> 
> ----- Original Message -----
> >      ? LTP lite
> 
> perf_event_open02 again:

I have a system [1] where it's consistently reproducible.
It looks like count_hardware_counters() reports incorrect number.
time_enabled and time_running are different but only barely (~0.7%).

# ./perf_event_open02 -v
at iteration:0 value:300357893 time_enabled:55368608 time_running:55368608
at iteration:1 value:600712498 time_enabled:54808179 time_running:54403148
perf_event_open02    0  TINFO  :  overall task clock: 54825931
perf_event_open02    0  TINFO  :  hw sum: 1442538620, task clock sum: 260919342
hw counters: 288507724 288507724 288507724 288507724 288507724
task clock counters: 51773047 52526664 52531694 52540386 51547551
perf_event_open02    0  TINFO  :  ratio: 4.759050
perf_event_open02    1  TFAIL  :  perf_event_open02.c:394: test failed (ratio was greater than )

Also do_work() completes pretty fast compared to a different host:

real	0m0.176s
user	0m0.163s
sys	0m0.003s

[1]
# lscpu 
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   36 bits physical, 48 bits virtual
CPU(s):                          4
On-line CPU(s) list:             0-3
Thread(s) per core:              2
Core(s) per socket:              1
Socket(s):                       2
NUMA node(s):                    1
Vendor ID:                       GenuineIntel
CPU family:                      15
Model:                           3
Model name:                      Intel(R) Xeon(TM) CPU 3.40GHz
Stepping:                        4
CPU MHz:                         2800.000
CPU max MHz:                     3400.0000
CPU min MHz:                     2800.0000
BogoMIPS:                        6800.62
L1d cache:                       32 KiB
L2 cache:                        2 MiB
NUMA node0 CPU(s):               0-3
Vulnerability L1tf:              Mitigation; PTE Inversion
Vulnerability Mds:               Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
Vulnerability Meltdown:          Mitigation; PTI
Vulnerability Spec store bypass: Vulnerable
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Full generic retpoline, STIBP disabled, RSB filling
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc pebs bts nopl cpui
                                 d pni dtes64 monitor ds_cpl est tm2 cid xtpr pti


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [LTP] ??? FAIL: Test report for kernel 5.4.0-rc6-dd89262.cki (mainline.kernel.org)
  2019-11-12  9:56   ` Jan Stancek
@ 2019-11-15  9:52     ` Cyril Hrubis
  0 siblings, 0 replies; 4+ messages in thread
From: Cyril Hrubis @ 2019-11-15  9:52 UTC (permalink / raw)
  To: ltp

Hi!
> > perf_event_open02 again:
> 
> I have a system [1] where it's consistently reproducible.
> It looks like count_hardware_counters() reports incorrect number.
> time_enabled and time_running are different but only barely (~0.7%).
> 
> # ./perf_event_open02 -v
> at iteration:0 value:300357893 time_enabled:55368608 time_running:55368608
> at iteration:1 value:600712498 time_enabled:54808179 time_running:54403148
> perf_event_open02    0  TINFO  :  overall task clock: 54825931
> perf_event_open02    0  TINFO  :  hw sum: 1442538620, task clock sum: 260919342
> hw counters: 288507724 288507724 288507724 288507724 288507724
> task clock counters: 51773047 52526664 52531694 52540386 51547551
> perf_event_open02    0  TINFO  :  ratio: 4.759050
> perf_event_open02    1  TFAIL  :  perf_event_open02.c:394: test failed (ratio was greater than )
> 
> Also do_work() completes pretty fast compared to a different host:
> 
> real	0m0.176s
> user	0m0.163s
> sys	0m0.003s

I was thinking of setting up an CPU time alarm that would stop that loop
so that it will run for reasonably defined length regardless the CPU
speed...

-- 
Cyril Hrubis
chrubis@suse.cz

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2019-11-15  9:52 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-11  8:05 [LTP] ❌ FAIL: Test report for kernel 5.4.0-rc6-dd89262.cki (mainline.kernel.org) CKI Project
2019-11-11 17:00 ` Jan Stancek
2019-11-12  9:56   ` Jan Stancek
2019-11-15  9:52     ` [LTP] ??? " Cyril Hrubis

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.