From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Robert Berger <gmane@reliableembeddedsystems.com>
Cc: yocto@yoctoproject.org
Subject: Re: automated hardware testing
Date: Mon, 14 Jul 2014 11:46:23 +0100 [thread overview]
Message-ID: <4137831.cdWht7PMij@peggleto-mobl5.ger.corp.intel.com> (raw)
In-Reply-To: <53BD0C5B.3090506@reliableembeddedsystems.com>
Hi Robert,
On Wednesday 09 July 2014 12:33:15 Robert Berger wrote:
> I just noticed this [1] and there are rumors that in the next release
> hardware testing will also work with yocto-autobuilder.
>
> I do have a couple of boards deployer in my lab and build with
> autobuilder images for them.
>
> The consoles of my boards are connected via conservers to ethernet and I
> can also remotely switch on/off power.
>
> For the beagle bone white the setup is more complex in order to press
> the reset button remotely and turn on/off the power over the USB cable
> remotely.
>
> My goal would be to build something with autobuilder, deploy to a board
> and run some tests.
>
> Is this feasible with my current infrastructure?
> Can someone please guide me in the right directions.
Absolutely. As a starting point I'd recommend the following section of the
manual:
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#performing-automated-runtime-testing
Some of the capabilities in this area were added after 1.6, i.e. they are
only in master.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2014-07-14 10:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 9:33 automated hardware testing Robert Berger
2014-07-14 10:46 ` Paul Eggleton [this message]
2014-08-03 16:41 ` gmane
2014-08-04 15:19 ` Paul Eggleton
2014-07-21 13:35 ` Stoicescu, CorneliuX
2014-08-03 16:45 ` gmane
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=4137831.cdWht7PMij@peggleto-mobl5.ger.corp.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=gmane@reliableembeddedsystems.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.