From: Alex Schuilenburg <alexs@ecoscentric.com>
To: ecos-maintainers@sources.redhat.com
Subject: eCos and RedBoot test farm
Date: Thu, 13 Feb 2003 09:24:00 -0000 [thread overview]
Message-ID: <3E4B643B.7080201@ecoscentric.com> (raw)
Hi Folks
Just to follow up all the conversations at FOSDEM about an eCos and
RedBoot test farm for the benefit of those not present.
eCosCentric are in the progress of rebuilding the eCos and RedBoot test
farm. This test farm will be similar to the one that was available at
Red Hat (only better ;-). As such, this test farm will be used to
validate eCos and RedBoot builds as well as execution of binaries.
Naturally the eCos and RedBoot maintainers within eCosCetric will derive
a lot of benefit from this and I would also like to make this test farm
freely available to *all* eCos and RedBoot maintainers but for
non-commercial use only. The farm will of course also be made available
for commercial use (e.g. validation of ports etc), but this kind of use
will have to be paid for to help maintain the farm.
(For the benefit of lurkers, it was almost a full time job maintaining
the old test farm - burning in new RedBoots, replacing/fixing
unresponsive boards, etc etc)
To clarify non-commercial use, only the results of builds and test runs
for public and sponsored boards will be published on the web (for all to
read). This will allow all the maintainers equal opportunity to validate
new or contributed code to public or sponsored boards. Also, only
maintainers will be allowed access to the boards in the farm, they will
not be public resources. The farm will also be capable of
driving/testing boards at remote sites, but again this will only be
permitted for non-commercial purposes only.
As stated previously, the intention is to provide a free resource to the
maintainers to allow them to identify and fix problems, test/verify
contributions, etc for eCos and RedBoot. Test results will also be made
public for the subset of public and sponsored boards running in the farm.
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.
It is eCosCentric's intention to use the test farm to certify their
paying customers' ports as well as to make the farm available
commercially for other commercial organisations to use, if there is
sufficient interest. The test farm will be housed in one of Paul's sheds
and eCosCentric will be paying for the net connection, etc, so the
service will cost us money to provide. However, by having board sponsors
and commercial customers we hope to meet these costs. Obviously no
guarantees on the availability of boards can be made as well as the test
farm - as can be expected with embedded hardware etc.
Cheers
-- Alex
next reply other threads:[~2003-02-13 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 9:24 Alex Schuilenburg [this message]
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
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=3E4B643B.7080201@ecoscentric.com \
--to=alexs@ecoscentric.com \
--cc=ecos-maintainers@sources.redhat.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).