public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Alex Schuilenburg <alexs@ecoscentric.com>
To: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: eCos bitrot
Date: Thu, 22 May 2003 11:38:00 -0000	[thread overview]
Message-ID: <3ECCB5B7.7020404@ecoscentric.com> (raw)

Hi Dudes

The eCosCentric test farm is making pretty good progress, most of it is 
not visible yet unfortunately (yes, my fault, I am kept occupied on 
other trivial but necessary stuff).

Anyway, here is a brief update:
* We are building perms and tests for various targets
* We are running automated tests for those targets
* Results are in raw log files which are easily turned into HTML,
   including summaries, although we are not wasting time tidying this as
   we are going for the final result: logging the results in the
   database.

The results so far for anoncvs have been very interesting:

Builds
------
*  1 perm now fails to configure
* 11 perms will no longer build
*  3 perms produce errors building tests (make tests error)
* *all* perms produce build warnings

Tests
-----
So far we have only put in the EBSA targets (courtesy ASCOM) as the 
other targets need work: For e.g. PID:- Need RedBoot in EPROM and we 
don't have a suitable programmer; PLC2 and LAKI:- need to get platform 
specific code and permission from ASCOM;

The EBSA has around a 90-95% pass rate for the tests that actually 
build, which is not bad considering.  All are timeouts (cache1, kcache1, 
etc). We (eCosCentric) are looking into these. I hope to have the build 
and test result display working within a week or so.  We can make the 
raw results available if anyone wants to jump the gun and fix the 
problems before the result pages are displayed - just let me know.

Jld is putting in some additional targets this afternoon and we should 
be up to 5-10% of the size the farm was at Red Hat shortly :-)  We need 
to extract the serial port terminal server from Bart and get that 
working to get more targets in place, although we are no longer 
restricted to requiring a serial port to determine reset OK.


Summary
-------
On the whole, we are pleased with the stability of the new farm. 
Results appear a lot more consistent (i.e. less noise and 
spurious/WFM-style errors) and we managed to run 4854 tests in a 24 hour 
period for a single platform.  So a full cycle should take around 3-4 
days insead of the usual 2 weeks.

We hope this will be a very useful resource for you and an extremely 
beneficial service for our customers.

Paul is the only one complaining as the rats have moved out the test 
farm and into his house because of the constant clacking ;-)

-- Alex



             reply	other threads:[~2003-05-22 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 11:38 Alex Schuilenburg [this message]
2003-05-22 11:52 ` Andrew Lunn
2003-05-22 12:28   ` 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=3ECCB5B7.7020404@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).