From: Mark Brown <broonie@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
lkft-triage@lists.linaro.org, Shuah Khan <shuah@kernel.org>,
Kees Cook <keescook@chromium.org>,
Anders Roxell <anders.roxell@linaro.org>,
Remi Duraffort <remi.duraffort@linaro.org>
Subject: Re: kselftest: Bad test result: from results parsing in LAVA
Date: Wed, 16 Nov 2022 13:27:48 +0000 [thread overview]
Message-ID: <Y3TlVAgo9XSWKm1h@sirena.org.uk> (raw)
In-Reply-To: <CA+G9fYu0p4cFdkrkQyV4OC-iPpY18asV0VTP=O_sysLNaJJAQw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
On Wed, Nov 16, 2022 at 05:46:33PM +0530, Naresh Kamboju wrote:
> kselftest running on LAVA infrastures provides test results parser
> from test-definitions repository.
> which is getting "Bad test result:".
>
> I have noticed this on kernelci [1] and LKFT LAVA instances [2].
> We need to investigate and change parse_output [3] inside test-definitions.
>
> Report-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Test results parser showing “Bad test results: “,
When reporting an issue can you please try to provide some
analysis which goes beyond the level of "I saw an error message"
- for example here it's hard to tell if you think you're seeing
an issue somewhere in your test automation system or if you're
trying to report something in the tests.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-11-16 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 12:16 Naresh Kamboju
2022-11-16 13:27 ` Mark Brown [this message]
2022-11-16 14:06 ` Naresh Kamboju
2022-11-16 16:02 ` Mark Brown
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=Y3TlVAgo9XSWKm1h@sirena.org.uk \
--to=broonie@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=remi.duraffort@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®