public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: poky@yoctoproject.org
Cc: paul.eggleton@linux.intel.com, benjamin.esquivel@intel.com,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] ptest-runner2 C implementation
Date: Mon, 18 Jan 2016 09:52:29 -0600	[thread overview]
Message-ID: <569D0A3D.2030102@linux.intel.com> (raw)
In-Reply-To: <cover.1452808370.git.anibal.limon@linux.intel.com>


ping...

On 01/14/2016 04:27 PM, Aníbal Limón wrote:
> This is the changes that adds new ptest-runner2 C implementation a detail
> description exists in the recipe adding.
> 
> You can review the ptest-runner2 code on [1], i wrote unit tests for all
> the code using check framework also i used mtrace for found possible memory leaks.
> 
> Finally i tested the new runner on qemux86, qemuarm, qemumips, qemuppc using
> core-image-minimal and qemux86/poky-tiny/core-image-minimal.
> 
> [YOCTO #8021]
> 
> [1] https://github.com/alimon/ptest-runner2
> 
> The following changes since commit 92cc02fe517bad0af4e493fda3331738cbcc9a26:
> 
>   linux-yocto: Update Genericx86* BSPs to 4.1.15 (2016-01-14 15:18:46 +0000)
> 
> are available in the git repository at:
> 
>   git://git.yoctoproject.org/poky-contrib alimon/ptest-runner2
>   http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=alimon/ptest-runner2
> 
> Aníbal Limón (3):
>   ptest-runner2: Add new ptest-runner2 recipe.
>   ptests: Update references to new ptest-runner2.
>   Update dev-manual to point to the new ptest-runner2.
> 
>  .../dev-manual/dev-manual-common-tasks.xml         |  4 ++--
>  meta/classes/ptest.bbclass                         |  2 +-
>  meta/lib/oeqa/runtime/_ptest.py                    |  4 ++--
>  .../ptest-runner2/ptest-runner2_0.1.bb             | 24 ++++++++++++++++++++++
>  4 files changed, 29 insertions(+), 5 deletions(-)
>  create mode 100644 meta/recipes-support/ptest-runner2/ptest-runner2_0.1.bb
> 


      parent reply	other threads:[~2016-01-18 15:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14 22:27 [PATCH 0/3] ptest-runner2 C implementation Aníbal Limón
2016-01-14 22:27 ` [PATCH 1/3] ptest-runner2: Add new ptest-runner2 recipe Aníbal Limón
2016-01-14 22:27 ` [PATCH 2/3] ptests: Update references to new ptest-runner2 Aníbal Limón
2016-01-14 22:27 ` [PATCH 3/3] Update dev-manual to point to the " Aníbal Limón
2016-01-18 15:52 ` Aníbal Limón [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=569D0A3D.2030102@linux.intel.com \
    --to=anibal.limon@linux.intel.com \
    --cc=benjamin.esquivel@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=poky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox