All of lore.kernel.org
 help / color / mirror / Atom feed
From: lkft@linaro.org
To: ltp@lists.linux.it
Cc: lkft-triage@lists.linaro.org
Subject: [LTP] [REGRESSION] lkft ltp for 13c674e
Date: Mon, 19 Sep 2022 17:34:00 +0000	[thread overview]
Message-ID: <0100018356d06195-5bf3efa5-c65f-4369-8a97-d588d0899dcd-000000@email.amazonses.com> (raw)

## Build
* kernel: 5.18.19
* git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
* git branch: linux-5.18.y
* git commit: 22a992953741ad79c07890d3f4104585e52ef26b
* git describe: 13c674e
* test details: https://qa-reports.linaro.org/lkft/ltp/build/13c674e

## Test Regressions (compared to 8ff3f5f)
* qemu_arm64, ltp-controllers
  - cpuacct_100_100

* qemu_i386, ltp-controllers
  - cpuacct_100_100


## Metric Regressions (compared to 8ff3f5f)
No metric regressions found.

Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>


## Test Fixes (compared to 8ff3f5f)
* bcm2711-rpi-4-b, ltp-syscalls
  - inotify11

* qemu_arm, ltp-syscalls
  - epoll_pwait01

* qemu_i386, ltp-cve
  - cve-2018-1000204


## Metric Fixes (compared to 8ff3f5f)
No metric fixes found.

## Test result summary
total: 12032, pass: 10202, fail: 156, skip: 1674, xfail: 0

## Build Summary

## Test suites summary
* log-parser-boot
* log-parser-test
* ltp-cap_bounds
* ltp-commands
* ltp-containers
* ltp-controllers
* ltp-cpuhotplug
* ltp-crypto
* ltp-cve
* ltp-dio
* ltp-fcntl-locktests
* ltp-filecaps
* ltp-fs
* ltp-fs_bind
* ltp-fs_perms_simple
* ltp-fsx
* ltp-hugetlb
* ltp-io
* ltp-ipc
* ltp-math
* ltp-mm
* ltp-nptl
* ltp-pty
* ltp-sched
* ltp-securebits
* ltp-syscalls
* ltp-tracing

--
Linaro LKFT
https://lkft.linaro.org

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

                 reply	other threads:[~2022-09-19 17:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=0100018356d06195-5bf3efa5-c65f-4369-8a97-d588d0899dcd-000000@email.amazonses.com \
    --to=lkft@linaro.org \
    --cc=lkft-triage@lists.linaro.org \
    --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.