From: Robert Berger <gmane@reliableembeddedsystems.com>
To: yocto@yoctoproject.org
Cc: Robert Berger
<public-gmane-G/ASJRsgvFgvW+L+VdN226ESeJV5RFUqQQ4Iyu8u01E@plane.gmane.org>,
public-yocto-EtnWKYl6rD/WsZ/bQMPhNw@plane.gmane.org
Subject: Re: [Announcement] Yocto Project 1.5 Milestone 3 now available.
Date: Sun, 11 Aug 2013 10:03:12 +0300 [thread overview]
Message-ID: <52073730.8080203@reliableembeddedsystems.com> (raw)
In-Reply-To: <3217805.kYDiUIXKQu@helios>
Hi,
On 08/10/2013 01:02 PM, Paul Eggleton wrote:
>
> The new framework replaces the old, is written in python and makes writing
> tests much easier. As a result we are going through a process of adding many
> more runtime tests than we had previously.
I'm confused now. Is it autobuilder + new stuff in python and/or ptest
or something completely different? Are there already some examples in
git I could have a look at?
>
>
> We do definitely want automated testing on real hardware; it's just that that
> it presents a number of problems that need solving:
>
> * How do you deploy the image/kernel/bootloader onto the board in an
> automated manner?
I use kernel over tftp and rootfs over nfs. The trivial example of a
boot loader upgrade is when you have a running (Linux) system just scp
it over. It's getting non trivial in case you manage to screw up the
boot loader. For the generic case maybe some update strategy with a
fallback solution to a known good boot loader might be needed.
> To different kinds of boards?
kernel over tftp and rootfs over nfs should work with all boards.
> * How do you manage access to the boards when you have multiple autobuilders
> potentially wanting to make use of them at around the same time?
Mutual exclusive access to the (serial) console can be handled by
conserver. Mutual exclusive via ssh gets more tricky.
I don't think it makes much sense to access the same board from multiple
autobuilders. This is most likely an error case which you would like to
catch.
>
> We'll be working through these but the likelihood is that we won't have this
> part of it for 1.5. Once we do though, connecting the currently QEMU-based
> testing framework to it should be trivial.
OK understood. Please keep me updated.
>
> Cheers,
> Paul
Regards,
Robert
...If you think good architecture is expensive, try bad architecture -
Brian Foote and Joseph Yoder
My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
next prev parent reply other threads:[~2013-08-11 7:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-10 0:22 [Announcement] Yocto Project 1.5 Milestone 3 now available Flanagan, Elizabeth
2013-08-10 7:20 ` Robert Berger
2013-08-10 10:02 ` Paul Eggleton
2013-08-11 7:03 ` Robert Berger [this message]
2013-08-12 9:44 ` Paul Eggleton
2013-08-13 8:21 ` Robert Berger
2013-08-12 9:11 ` Björn Stenberg
2013-08-12 9:28 ` Paul Eggleton
2013-08-12 11:30 ` Björn Stenberg
2013-08-13 8:15 ` Robert Berger
2013-08-13 10:33 ` Björn Stenberg
2013-08-13 8:18 ` Robert Berger
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=52073730.8080203@reliableembeddedsystems.com \
--to=gmane@reliableembeddedsystems.com \
--cc=public-gmane-G/ASJRsgvFgvW+L+VdN226ESeJV5RFUqQQ4Iyu8u01E@plane.gmane.org \
--cc=public-yocto-EtnWKYl6rD/WsZ/bQMPhNw@plane.gmane.org \
--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.