From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCHv2 0/3] Upgrades for comply Intel Graphics Stack Release 2014Q3
Date: Wed, 10 Dec 2014 16:21:54 +0000 [thread overview]
Message-ID: <1418228514.22903.65.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKpZ9bHJOnjLthir2XNntSORzEQUNe0jE2DJptLoL6Vr9Q@mail.gmail.com>
On Wed, 2014-12-10 at 14:17 -0200, Otavio Salvador wrote:
> On Wed, Dec 10, 2014 at 2:15 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Tue, 2014-12-09 at 18:19 -0200, Otavio Salvador wrote:
> >> On Tue, Dec 9, 2014 at 6:06 PM, Burton, Ross <ross.burton@intel.com> wrote:
> >> >
> >> > On 9 December 2014 at 18:14, Aníbal Limón <anibal.limon@linux.intel.com>
> >> > wrote:
> >> >>
> >> >> I don't know, maybe Ross knows?.
> >> >
> >> >
> >> > I ask for Piglit results to verify that approx 95% passes as that's the
> >> > expected pass rate. I don't bother tracking the exact count as how it
> >> > changes as there's almost ten thousand tests and at some point you have to
> >> > let upstream deal with this.
> >>
> >> What is the point in having a tool for regression test if it is not tracked?
> >
> > Going forward, the plan is to track this FWIW. Right now that is a work
> > in progress as the test result collection piece is missing. Its also a
> > chicken and egg problem, you can't track things until you have some
> > tests to track. Things are being run manually to check for regressions
> > in a coarse manner too and this is better than not at all.
>
> Well, when asked Ross said he is not tracking this data. So the question...
He personally isn't and he had valid reasons for looking at an overall
percentage rather than individual scores, but the QA people working on
the project are working towards tracking the data. Once we can track it,
we will need some ways of analysing the data as that in itself is
tricky.
Cheers,
Richard
next prev parent reply other threads:[~2014-12-10 16:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 23:18 [PATCHv2 0/3] Upgrades for comply Intel Graphics Stack Release 2014Q3 Aníbal Limón
2014-12-04 23:18 ` [PATCHv2 1/3] libdrm: Upgrade to 2.4.58 Aníbal Limón
2014-12-04 23:18 ` [PATCHv2 2/3] mesa: Upgrade to 10.3.4 Aníbal Limón
2014-12-04 23:18 ` [PATCHv3 3/3] xorg-xserver: Upgrade to 1.16.2 Aníbal Limón
2014-12-08 9:29 ` [PATCHv2 0/3] Upgrades for comply Intel Graphics Stack Release 2014Q3 Nicolas Dechesne
2014-12-09 17:20 ` Kamble, Nitin A
2014-12-09 18:14 ` Aníbal Limón
2014-12-09 20:06 ` Burton, Ross
2014-12-09 20:19 ` Otavio Salvador
2014-12-10 11:43 ` Burton, Ross
2014-12-10 16:15 ` Richard Purdie
2014-12-10 16:17 ` Otavio Salvador
2014-12-10 16:21 ` Richard Purdie [this message]
2014-12-10 8:08 ` Nicolas Dechesne
2014-12-10 11:33 ` Burton, Ross
2014-12-10 15:46 ` Aníbal Limón
2014-12-10 23:43 ` Kamble, Nitin A
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=1418228514.22903.65.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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