From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: niklaus.giger@domain.hid
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [RFC] collecting xenomai statistics
Date: Tue, 18 Apr 2006 19:39:28 +0200 [thread overview]
Message-ID: <17477.9296.484358.469533@domain.hid> (raw)
In-Reply-To: <200604171047.51730.niklaus.giger@domain.hid>
Niklaus Giger wrote:
> But I would be very interested in knowing exactly which kind of information
> the core developers are interested in. How should it be presented? In tabular
> form? Graphs, which ones? And kind of feedback will be evaluated and
> integrated.
I did some similar work once, so I have some ideas. What I
would like to have is, given a configuration (.config) build all
versions of Adeos+Xenomai for a given set of compilers. Then, present
the result in a tabular form. Each cell would give the number of
warnings and errors for the corresponding build, with links to
browseable build logs. Maybe the cell could have different colors
(green, orange, red) depending on the number of warnings and errors.
What would also be interesting, is to test the "distcheck" target. The
interesting result being a comparison between the source directory
contents and the generated tarball contents (if distcheck is
successful).
--
Gilles Chanteperdrix.
prev parent reply other threads:[~2006-04-18 17:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 8:47 [Xenomai-core] [RFC] collecting xenomai statistics Niklaus Giger
2006-04-17 21:13 ` Jan Kiszka
2006-04-18 2:10 ` Jim Cromie
2006-04-18 15:32 ` [Xenomai-core] [patch] xeno-test email addition Jim Cromie
2006-04-18 15:58 ` Philippe Gerum
2006-04-19 3:55 ` Romain Lenglet
2006-04-19 9:01 ` Philippe Gerum
2006-04-19 12:52 ` Jim Cromie
2006-04-20 21:01 ` Philippe Gerum
2006-04-18 17:02 ` [Xenomai-core] [RFC] collecting xenomai statistics Gilles Chanteperdrix
2006-04-18 17:15 ` Gilles Chanteperdrix
2006-04-18 17:39 ` Gilles Chanteperdrix [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=17477.9296.484358.469533@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=niklaus.giger@domain.hid \
--cc=xenomai@xenomai.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.