linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, lkft-triage@lists.linaro.org,
	Linux Kernel Functional Testing <lkft@linaro.org>
Subject: Re: Linux v5.18
Date: Mon, 23 May 2022 17:14:38 +0530	[thread overview]
Message-ID: <20220523114438.30160-1-naresh.kamboju@linaro.org> (raw)
In-Reply-To: <CAHk-=wjiqyoH6qntYvYTjR1F2L-pHtgX9esZMRS13iktCOJ1zA@mail.gmail.com>

Results from Linaro’s test farm.
No regressions on arm64, arm, x86_64, and i386.

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

## Build
* kernel: 5.18.0
* git: https://gitlab.com/Linaro/lkft/mirrors/torvalds/linux-mainline
* git branch: master
* git commit: 4b0986a3613c92f4ec1bdc7f60ec66fea135991f
* git describe: v5.18
* test details: https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v5.18

## Test Regressions (compared to v5.18-rc7-185-g978df3e15846)
No test regressions found.

## Metric Regressions (compared to v5.18-rc7-185-g978df3e15846)
No Metric regressions found.

## Test Fixes (compared to v5.18-rc7-185-g978df3e15846)
No test fixes found.

## Metric Fixes (compared to v5.18-rc7-185-g978df3e15846)
No metric fixes found.

## Test result summary
total: 95781, pass: 82937, fail: 698, skip: 11135, xfail: 1011

## Build Summary
* arc: 10 total, 10 passed, 0 failed
* arm: 301 total, 295 passed, 6 failed
* arm64: 54 total, 52 passed, 2 failed
* i386: 49 total, 45 passed, 4 failed
* mips: 45 total, 38 passed, 7 failed
* parisc: 16 total, 16 passed, 0 failed
* powerpc: 70 total, 57 passed, 13 failed
* riscv: 37 total, 27 passed, 10 failed
* s390: 31 total, 25 passed, 6 failed
* sh: 28 total, 24 passed, 4 failed
* sparc: 16 total, 14 passed, 2 failed
* x86_64: 53 total, 50 passed, 3 failed

## Test suites summary
* fwts
* igt-gpu-tools
* kselftest-android
* kselftest-arm64
* kselftest-breakpoints
* kselftest-capabilities
* kselftest-cgroup
* kselftest-clone3
* kselftest-core
* kselftest-cpu-hotplug
* kselftest-cpufreq
* kselftest-drivers
* kselftest-efivarfs
* kselftest-filesystems
* kselftest-firmware
* kselftest-fpu
* kselftest-futex
* kselftest-gpio
* kselftest-intel_pstate
* kselftest-ipc
* kselftest-ir
* kselftest-kcmp
* kselftest-kexec
* kselftest-kvm
* kselftest-lib
* kselftest-livepatch
* kselftest-membarrier
* kselftest-memfd
* kselftest-memory-hotplug
* kselftest-mincore
* kselftest-mount
* kselftest-mqueue
* kselftest-net
* kselftest-openat2
* kselftest-pid_namespace
* kselftest-pidfd
* kselftest-proc
* kselftest-pstore
* kselftest-ptrace
* kselftest-rseq
* kselftest-rtc
* kselftest-seccomp
* kselftest-sigaltstack
* kselftest-size
* kselftest-splice
* kselftest-static_keys
* kselftest-sync
* kselftest-sysctl
* kselftest-timens
* kselftest-timers
* kselftest-tmpfs
* kselftest-tpm2
* kselftest-user
* kselftest-vm
* kselftest-x86
* kselftest-zram
* kunit
* kunit/15
* kunit/261
* kunit/3
* kunit/427
* kunit/90
* kvm-unit-tests
* libgpiod
* libhugetlbfs
* linux-log-parser
* ltp-cap_bounds-tests
* ltp-commands-tests
* ltp-containers-tests
* ltp-controllers-tests
* ltp-cpuhotplug-tests
* ltp-crypto-tests
* ltp-cve-tests
* ltp-dio-tests
* ltp-fcntl-locktests-tests
* ltp-filecaps-tests
* ltp-fs-tests
* ltp-fs_bind-tests
* ltp-fs_perms_simple-tests
* ltp-fsx-tests
* ltp-hugetlb-tests
* ltp-io-tests
* ltp-ipc-tests
* ltp-math-tests
* ltp-mm-tests
* ltp-nptl-tests
* ltp-open-posix-tests
* ltp-pty-tests
* ltp-sched-tests
* ltp-securebits-tests
* ltp-syscalls-tests
* ltp-tracing-tests
* network-basic-tests
* packetdrill
* perf
* prep-inline/Zstd-perf.data-compression
* rcutorture
* ssuite
* v4l2-compliance
* vdso

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

      parent reply	other threads:[~2022-05-23 11:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-22 20:02 Linux 5.18 Linus Torvalds
2022-05-22 23:21 ` Guenter Roeck
2022-05-23  7:35 ` Build regressions/improvements in v5.18 Geert Uytterhoeven
2022-05-23 11:44 ` Naresh Kamboju [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=20220523114438.30160-1-naresh.kamboju@linaro.org \
    --to=naresh.kamboju@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=lkft@linaro.org \
    --cc=torvalds@linux-foundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).