From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Dilip Kumar <008dilip@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Yocto test tools for performance and stability
Date: Fri, 08 Nov 2013 10:26:50 +0000 [thread overview]
Message-ID: <3266718.IQu0dQtgCC@helios> (raw)
In-Reply-To: <CABmxB3ME=E5FzYqs-fW5k8Bx3VT_Jk8wLi_kzoGzSCUe3dhnng@mail.gmail.com>
Hi Dilip,
On Thursday 07 November 2013 11:22:22 Dilip Kumar wrote:
> May I know the list of Yocto provided test tools for performance and
> stability and how enable and use the test tools
For the 1.5 (dora) release we have added automated runtime testing (on
top of QEMU only for now):
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#performing-automated-runtime-testing
We have a number of planned enhancements in this area. There are enhancement
bugs open for each one:
https://bugzilla.yoctoproject.org/buglist.cgi?product=Automated%20Runtime%20Testing&component=automated-runtime-testing&resolution=---&list_id=125679
We are also planning to extend testing of the build system itself:
https://bugzilla.yoctoproject.org/buglist.cgi?product=Automated%20Build%20Testing&component=automated-build-testing&resolution=---&list_id=125677
We currently track build performance by running a script on a regular basis,
see here for details:
https://wiki.yoctoproject.org/wiki/Performance_Test
We don't currently track runtime performance, but there are enhancement bugs
open for that:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4144
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4528
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-11-08 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 5:52 Yocto test tools for performance and stability Dilip Kumar
2013-11-08 10:26 ` Paul Eggleton [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=3266718.IQu0dQtgCC@helios \
--to=paul.eggleton@linux.intel.com \
--cc=008dilip@gmail.com \
--cc=yocto@yoctoproject.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.