From: ci_notify@linaro.org
To: lkft-triage@lists.linaro.org, dan.rue@linaro.org,
anders.roxell@linaro.org, naresh.kamboju@linaro.org,
shuah@kernel.org, linux-kselftest@vger.kernel.org
Subject: next-20200412 kselftest results
Date: Sun, 12 Apr 2020 09:00:28 +0000 (UTC) [thread overview]
Message-ID: <1384417092.17074.1586682029011.JavaMail.javamailuser@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 1604 bytes --]
Summary
------------------------------------------------------------------------
kernel: 5.6.0
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git branch: master
git commit: d2a22790db7075dbd0738d24d1c5ee4611421c4c
git describe: next-20200412
Test details: https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20200412
Regressions (compared to build next-20200411)
------------------------------------------------------------------------
No regressions
Fixes (compared to build next-20200411)
------------------------------------------------------------------------
No fixes
In total:
------------------------------------------------------------------------
Ran 0 total tests in the following environments and test suites.
pass 0
fail 0
xfail 0
skip 0
Environments
--------------
- dragonboard-410c - arm64
- hi6220-hikey - arm64
- i386
- juno-r2 - arm64
- juno-r2-compat
- juno-r2-kasan
- x86_64
- x86-kasan
Test Suites
-----------
Failures
------------------------------------------------------------------------
juno-r2:
i386:
juno-r2-compat:
juno-r2-kasan:
x86:
dragonboard-410c:
Skips
------------------------------------------------------------------------
No skips
--
Linaro LKFT
https://lkft.linaro.org
reply other threads:[~2020-04-12 9:00 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=1384417092.17074.1586682029011.JavaMail.javamailuser@localhost \
--to=ci_notify@linaro.org \
--cc=anders.roxell@linaro.org \
--cc=dan.rue@linaro.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=shuah@kernel.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 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.