[Tinyos-devel] cruisecontrol now testing for safe tinyos

[Philip Levis]

On Jul 7, 2008, at 11:02 AM, Jan Beutel wrote:

> hello all,
>
> i installed a current and patched tinyos-2.x toolchain today and the
> "standard apps" are now built both for unsafe and safe for a number of
> platforms. for those of you testing for the 2.1 release, you can go  
> and
> snatch the compiled binaries under the "artifacts" link. this ensures,
> that e.g. two people testing are testing the same binary.
>
> http://tik42x.ee.ethz.ch:8080
>
> here are some details for the m-oscope application compiled for the
> platforms eyes, mica2/dot/z, shimmer, telosba and tinynode:
>
> general overview:
>
> http://tik42x.ee.ethz.ch:8080/buildresults/t2-multihoposcilloscope
>
> build artifacts (app.c, .exe, .hex and .xml files) for both unsafe:
>
> http://tik42x.ee.ethz.ch:8080/artifacts/t2-multihoposcilloscope/20080707192347/builds/telosb
>
> and safe:
>
> http://tik42x.ee.ethz.ch:8080/artifacts/t2-multihoposcilloscope/20080707192347/builds-safe/telosb
>
> memory consumption for all platforms (unsafe)
>
> http://tik42x.ee.ethz.ch:8080/buildresults/t2-multihoposcilloscope?tab=tos-metrics
>
> power metrics for telosb and tinynode
>
> http://tik42x.ee.ethz.ch:8080/buildresults/t2-multihoposcilloscope?tab=power-metrics
> http://tik42x.ee.ethz.ch:8080/buildresults/t2-multihoposcilloscope?tab=power-charts
>
> i will try to get a graphical reporting of the memory usage and power
> consumption online asap. for the moment being you can see the memory
> consumption for safe builds here:
>
> http://tik42x.ee.ethz.ch:8080/artifacts/t2-multihoposcilloscope/20080707192347/logs-safe/telosb/msp430-size.xml
>
> ahh and last but not least for those of you that care about tool
> versions: i am building on kevin klues current patched compiler/libc
> toolchain with tinyos-2.x/tools, nesC and deputy from CVS/SVN HEAD  
> on an
> x86 host platform. so it is always "slightly" newer than the debian
> packages...
>
> best,
>
> jan

Jan, this is really, really cool.

Have you thought about compiling with LPL enabled?

Phil