From: Dan Rue <dan.rue@linaro.org>
To: shuah <shuah@kernel.org>
Cc: "Anders Roxell" <anders.roxell@linaro.org>,
"Daniel Díaz" <daniel.diaz@linaro.org>,
lkft-triage@lists.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: Tue, 8 Oct 2019 15:31:27 -0500 [thread overview]
Message-ID: <20191008203127.6ifehxzrz5ruxz6m@xps.therub.org> (raw)
In-Reply-To: <434b3683-77c0-0a11-80e5-3329b5d20069@kernel.org>
On Thu, Oct 03, 2019 at 02:03:28PM -0600, shuah wrote:
> On 10/2/19 8:47 PM, Anders Roxell wrote:
> > On Thu, 3 Oct 2019 at 04:15, Daniel Díaz <daniel.diaz@linaro.org> wrote:
> > >
> > > 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
> >
>
> Too many mouse click chasing these logs. Can you make this link on the
> dashboard.
Hi Shuah -
I agree, and I'm sorry but I am not sure how to make it better in the
near term - qa-reports is a generic interface and so it would be
difficult to show so many links on the summary screen.
What I'd like to do, but it won't help anytime soon, is generate better
reports and have the links in the report. Unfortunately it would be
pretty difficult to do that in a text based email report and using our
current tools. We are actively evaluating better reporting tools, but I
don't expect to have anything running until early next year at the
earliest.
Thank you for the feedback. If you have any other questions I'm happy to
see what we can do.
Dan
>
> thanks,
> -- Shuah
--
Linaro - Kernel Validation
prev parent reply other threads:[~2019-10-08 20:31 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
2019-10-03 2:47 ` Anders Roxell
2019-10-03 20:03 ` shuah
2019-10-08 20:31 ` Dan Rue [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=20191008203127.6ifehxzrz5ruxz6m@xps.therub.org \
--to=dan.rue@linaro.org \
--cc=anders.roxell@linaro.org \
--cc=daniel.diaz@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).