From: "Jair Gonzalez" <jair.de.jesus.gonzalez.plascencia@linux.intel.com>
To: <ed.bartosh@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 0/4] selftest/wic: extending test coverage for WIC script options
Date: Tue, 20 Dec 2016 16:04:06 -0600 [thread overview]
Message-ID: <017801d25b0c$fbd79330$f386b990$@linux.intel.com> (raw)
In-Reply-To: <20161220130651.GA16237@linux.intel.com>
> -----Original Message-----
> From: Ed Bartosh [mailto:ed.bartosh@linux.intel.com]
> Sent: Tuesday, December 20, 2016 7:07 AM
> To: Jair Gonzalez <jair.de.jesus.gonzalez.plascencia@linux.intel.com>
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH v2 0/4] selftest/wic: extending test
coverage
> for WIC script options
>
> On Mon, Dec 19, 2016 at 03:07:30PM -0600, Jair Gonzalez wrote:
> > Changed in V2:
> >
> > The original patch was splitted and updated according to the
discussion on:
> > http://lists.openembedded.org/pipermail/openembedded-core/2016-
> Decembe
> > r/130131.html
> > NOTE: The WKS_FILE entry deletion was ommitted from this patch set as
> > it was introduced on the first patch by mistake.
> >
> > The following changes since commit
> 573c646d4cc62dcd0c230381df4940bdf314d495:
> >
> > bitbake: BBHandler: use with instead of open/close (2016-12-16
> > 10:23:24 +0000)
> >
> > are available in the git repository at:
> >
> > git://git.yoctoproject.org/poky-contrib jairglez/wictest
> >
> > http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=jairglez/wict
> > est
> >
> > Jair Gonzalez (4):
> > selftest/wic: adding Testopia ID numbers to test cases missing it
> > selftest/wic: code cleanup
> > selftest/wic: reorganizing test methods by functionality
> > selftest/wic: extending test coverage for WIC script options
> >
> > meta/lib/oeqa/selftest/wic.py | 370
> > +++++++++++++++++++++++++++---------------
> > 1 file changed, 238 insertions(+), 132 deletions(-)
> >
>
> Thank you for the updated patchset!
> It looks good to me.
>
> BTW, did you measure its impact on the test run time?
>
> --
> Regards,
> Ed
Hi Ed,
Thanks. Regarding the impact, I tested it on my local machine after cleaning
the cache, sstate-cache, downloads and tmp directories, and the difference
between them was about 130 seconds after I applied my commits:
Before:
Ran 28 tests in 4446.939s
After:
Ran 39 tests in 4578.604s
Difference:
131.665s
I also tried with a source repository with existing cache and the difference
was about 70 seconds:
Before:
Ran 28 tests in 272.170s
After:
Ran 39 tests in 339.637s
Difference:
67.467s
Regards,
Jair
next prev parent reply other threads:[~2016-12-20 22:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 21:07 [PATCH v2 0/4] selftest/wic: extending test coverage for WIC script options Jair Gonzalez
2016-12-19 21:07 ` [PATCH v2 1/4] selftest/wic: adding Testopia ID numbers to test cases missing it Jair Gonzalez
2016-12-19 21:07 ` [PATCH v2 2/4] selftest/wic: code cleanup Jair Gonzalez
2016-12-19 21:07 ` [PATCH v2 3/4] selftest/wic: reorganizing test methods by functionality Jair Gonzalez
2016-12-19 21:07 ` [PATCH v2 4/4] selftest/wic: extending test coverage for WIC script options Jair Gonzalez
2016-12-20 13:06 ` [PATCH v2 0/4] " Ed Bartosh
2016-12-20 22:04 ` Jair Gonzalez [this message]
2016-12-21 13:06 ` Ed Bartosh
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='017801d25b0c$fbd79330$f386b990$@linux.intel.com' \
--to=jair.de.jesus.gonzalez.plascencia@linux.intel.com \
--cc=ed.bartosh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.