From: Cristian Marussi <cristian.marussi@arm.com>
To: ci_notify@linaro.org, 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
Cc: Prabhakar Kushwaha <pkushwaha@marvell.com>
Subject: Re: next-20191024 kselftest results
Date: Thu, 24 Oct 2019 11:48:58 +0100 [thread overview]
Message-ID: <cb6b01a2-11a6-b33d-98cc-dea60933aff0@arm.com> (raw)
In-Reply-To: <312839085.10341.1571900438441.JavaMail.javamailuser@localhost>
Hi
On 24/10/2019 08:00, ci_notify@linaro.org wrote:
> Summary
> ------------------------------------------------------------------------
> kernel: 5.4.0-rc4
> git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git branch: master
> git commit: 12d61c6996999e6562cbbed5f270d572248a11c5
> git describe: next-20191024
> Test details: https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20191024
>
> Regressions (compared to build next-20191023)
> ------------------------------------------------------------------------
> No regressions
>
> Fixes (compared to build next-20191023)
> ------------------------------------------------------------------------
> No fixes
>
> In total:
> ------------------------------------------------------------------------
> Ran 0 total tests in the following environments and test suites.
> pass 0
> fail 0
> xfail 0
> skip 0
>
It seems that my previous patch meant to ease kselftest in CI:
[PATCH v2 2/2] kselftest: exclude failed TARGETS from runlist
https://lore.kernel.org/linux-kselftest/20190926175219.29805-3-cristian.marussi@arm.com/
contained a subtle bug that killed it worldwide indeed :<
it should have been fixed already by Prabhakar Kushwaha in:
[PATCH][v3] kselftest: Fix NULL INSTALL_PATH for TARGETS runlist
https://lore.kernel.org/linux-kselftest/1571750829-28944-1-git-send-email-pkushwaha@marvell.com/T/#u
Thanks for the patience...
Cristian
> Environments
> --------------
> - dragonboard-410c - arm64
> - hi6220-hikey - arm64
> - i386
> - juno-r2 - arm64
> - x15 - arm
> - x86_64
>
> Test Suites
> -----------
>
>
> Failures
> ------------------------------------------------------------------------
>
> i386:
>
> x86:
>
> x15:
>
> juno-r2:
>
> dragonboard-410c:
>
> hi6220-hikey:
>
>
> Skips
> ------------------------------------------------------------------------
> No skips
>
>
next prev parent reply other threads:[~2019-10-24 10:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 7:00 next-20191024 kselftest results ci_notify
2019-10-24 10:48 ` Cristian Marussi [this message]
2019-10-24 12:25 ` Daniel Díaz
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=cb6b01a2-11a6-b33d-98cc-dea60933aff0@arm.com \
--to=cristian.marussi@arm.com \
--cc=anders.roxell@linaro.org \
--cc=ci_notify@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=pkushwaha@marvell.com \
--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 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).