From: "Daniel Díaz" <daniel.diaz@linaro.org>
To: shuah <shuah@kernel.org>
Cc: lkft-triage@lists.linaro.org, Dan Rue <dan.rue@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>
Subject: Re: next-20191002 kselftest results
Date: Wed, 2 Oct 2019 21:15:45 -0500 [thread overview]
Message-ID: <CAEUSe7_+RQ9UPjJW1TzFwfCpcFuOv9ha7k_Lf46RJTg-=gVf_Q@mail.gmail.com> (raw)
In-Reply-To: <09618fd2-eb41-5a82-3fb4-4f4ca18bd075@kernel.org>
Hello!
On Wed, 2 Oct 2019 at 20:52, shuah <shuah@kernel.org> wrote:
>
> On 10/2/19 7:00 AM, ci_notify@linaro.org wrote:
> > Summary
> > ------------------------------------------------------------------------
> > kernel: 5.4.0-rc1
> > git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > git branch: master
> > git commit: a32db7e1172439240202b843642465618498170d
> > git describe: next-20191002
> > Test details: https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20191002
> >
> > Regressions (compared to build next-20191001)
>
> This report is nice for quick glance of test pass/fail/skip dashboard.
> I am finding very difficult to figure out why the test failed.
>
> Can you please save the test run logs and stash them for access?
Logs are saved. You can click on the test details:
https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20191002
then opening "kselftests" in Test Results, choosing an environment
(say "x86_64"), and then (here's the tricky one) "job_url":
https://lkft.validation.linaro.org/scheduler/job/948404
Running kselftests starts in line 1276 in that particular log.
Hope that sheds some light on that.
Greetings!
Daniel Díaz
daniel.diaz@linaro.org
next prev parent reply other threads:[~2019-10-03 2:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 13:00 next-20191002 kselftest results ci_notify
2019-10-03 1:52 ` shuah
2019-10-03 2:15 ` Daniel Díaz [this message]
2019-10-03 2:47 ` Anders Roxell
2019-10-03 20:03 ` shuah
2019-10-08 20:31 ` Dan Rue
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='CAEUSe7_+RQ9UPjJW1TzFwfCpcFuOv9ha7k_Lf46RJTg-=gVf_Q@mail.gmail.com' \
--to=daniel.diaz@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 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).