From: Shuah Khan <skhan@linuxfoundation.org>
To: Justin Cook <justin.cook@linaro.org>
Cc: LKFT <lkft@linaro.org>,
lkft-triage@lists.linaro.org, linux-kselftest@vger.kernel.org,
linux-next@vger.kernel.org, sfr@canb.auug.org.au,
shuah@kernel.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [REGRESSION] kselftest: next-20200915
Date: Thu, 17 Sep 2020 10:10:49 -0600 [thread overview]
Message-ID: <0263c321-5d2d-8822-6ed9-3ea24efce4dd@linuxfoundation.org> (raw)
In-Reply-To: <CANKHsTeOix88zT=d1ywROXXXZRxYnYOEzRQDJGJgoh4DVbnPjQ@mail.gmail.com>
Hi Justin,
On 9/17/20 9:52 AM, Justin Cook wrote:
> Shuah,
>
> The report sent was meant to be a general summary, rather than a deep
> dive, of the results. Most of that information can be gathered by
> viewing the test details.
>
>> * Test details:
>> https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20200915
>
> If you open that link in a web browser, there are a number of ways to
> dig down into the results. If you have questions about the best ways
> to do this, please let me know.
>
Yes. I did look at the results. It isn't easy to figure out. It would
help is cc'ing the test authors in addition to the list. There are two
failed tests if recall correctly, mm and kvm. cc'ing and subsystem
mailing lists and authors for the last commit for the test in question
will get you results quickly.
> Maybe that isn't the best way? I'm very open to feedback. I just tried
> to best copy the previous report that was being sent out to start.
>
We had the same problem with the previous report. It just tells you
which tests regressed. It is a good start. Unfortunately without
tagging test authors/maintainers it won't get addressed.
thanks,
-- Shuah
prev parent reply other threads:[~2020-09-17 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 17:44 [REGRESSION] kselftest: next-20200915 LKFT
2020-09-15 17:54 ` Justin Cook
[not found] ` <CANKHsTfyE64ygNB0H0Nx=P63D-kqYa6aGOXS6ZmNUspLJJtS=Q@mail.gmail.com>
2020-09-15 20:18 ` Shuah Khan
2020-09-17 15:52 ` Justin Cook
2020-09-17 16:10 ` Shuah Khan [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=0263c321-5d2d-8822-6ed9-3ea24efce4dd@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=justin.cook@linaro.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=lkft@linaro.org \
--cc=sfr@canb.auug.org.au \
--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