From: Alex Schuilenburg <alexs@ecoscentric.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Andrew Lunn <andrew.lunn@ascom.ch>, ecos-maintainers@sources.redhat.com
Subject: Re: eCos and RedBoot test farm
Date: Thu, 13 Feb 2003 15:37:00 -0000 [thread overview]
Message-ID: <3E4BBBB9.90007@ecoscentric.com> (raw)
In-Reply-To: <1045147499.8976.6295.camel@hermes.chez-thomas.org>
Hi Gary
Gary Thomas wrote:
> On Thu, 2003-02-13 at 02:30, Andrew Lunn wrote:
>
>>>Andrew, Gary and Mark - please let me know if you are interested in
>>>having access to such a facility or have any problems, suggestions etc
>>>with our offer.
>>
>>Yes please.
>>
>>One suggestion. Make access to it firewall friendly. Outgoing SSH and
>>https get through Ascom's firewall, but not a lot else. Incoming it
>>totally blocked.
>
>
> Moi, aussi, merci :-)
>
> SSH is the only way to go as far as I'm concerned as well.
>
> Alex, what sort of hardware do you have available?
We probably have less h/w than you, but they are slowly coming in as the
contracts come in.
The public boards we have are some MIPS & PPC boards, a Viper board, an
iPAQ and hopefully will have some more ARM platforms (EBSA285, Assabet,
etc) in the next couple of days. I don't have a complete list of
targets since the h/w is spread out a bit between the guys here and I
have lost track a bit :-)
We still have to clean out Paul's shed and get the wireless connection
working reliably before we can do that.
> I'm building up quite a set here, and if the infrastructure was
> such that it can easily run outside of Cambridge, I'd be interested
> in supporting what I can here.
>
Thanks. The infra will be such that boards can be remote but builds and
execution will be done from the farm so that results will be available
in one place for all maintainers to see. Traffic should still be
minimal (gdb download via ssh tunnel) though debug speeds may be slow -
but it should not matter much anyway as it will be automated.
We also intend to add the facility for complete email logs of test runs
to be added (ala GUI config-tool) to the results to allow
non-maintainers to submit results (e.g. contribs of h/w ports we/you
dont have access to), say as a pre-requisite for a port being accepted.
The actual test farm infra (automated checkouts, perms, builds and
executions) we intend to keep closed as it will be a commercial entity,
hopefully earning enough money to keep itself ticking and pay the bills.
If it does not become profitable, then it may be open sourced later.
Cheers
-- Alex
prev parent reply other threads:[~2003-02-13 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 9:24 Alex Schuilenburg
2003-02-13 9:30 ` Andrew Lunn
2003-02-13 10:04 ` Alex Schuilenburg
2003-02-13 14:45 ` Gary Thomas
2003-02-13 15:37 ` Alex Schuilenburg [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=3E4BBBB9.90007@ecoscentric.com \
--to=alexs@ecoscentric.com \
--cc=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@sources.redhat.com \
--cc=gary@mlbassoc.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).