Hi

During the last two weeks I spent several evenings to bring the buildbot back 
into a good shape.

Please take a look at http://ngiger.dyndns.org/buildbot/ to see the some of 
the results.

I upgraded to the 0.7.6 buildbot revision which has a much improved web display.

It is therefore possible to limit one's view to specific branches (2.3.x/2.4.x/
2.5.x at the moment or just a specifiy builder (e.g. i386_f). I hope that this
makes looking for specific errors easier for everybody.

Most builder use a new approach. As before the buildbot checks out the desired
trunk/branch/tag, downloads the config and (if necessary) a board specific 
patch.
Then the attached make_xenomai.rb Ruby creates a script to checkout the desired
git branch, running the prepare-kernel.sh, configure, make etc. A short for is
available as in
http://ngiger.dyndns.org/buildbot/builders/yosemite_f/builds/0/steps/genscript/logs/cmd2run
The full script (which each line surrounded by a if ! cmd ; then exit 2; fi) is
then run. This approach should ease a developpers work to reproduce the 
environment
where the buildbot reported an error.

In the next few days (beside Christmas with my familiy, some skiing and friends)
I will improve it to handle "old" version like 2.3.x correctly. Also I will I
builds of the most recent tags in the 2.3. and 2.4 line. Or does someone see the
need for lines like 2.2/2.1 or 2.0?

Also planned is to add one ore more boards to running xeno-test, the Yosemite 
(PPC440EP based) and HCU3 (PPC405GPr based).

If somebody would like to add more boards please drop me an email (may be with
an attached config and a script to show how the build was done).

Now about the failures I noticed:

a) The simulator fails in two tests with the vxworks skins. In
http://ngiger.dyndns.org/buildbot/builders/sim_f/builds/1/steps/check_sim/logs/stdio
you will find at the end the lines
> Some problems were reported in:
> vxworks->t010726-1::
> vxworks->t010823-2::
Going back one finds:
> starting VxWorks services.
> Xenoscope: lt-t010823-2: fatal in MvmIrq (time=30000718.974563):
> test interrupted by watchdog.
and
> starting VxWorks services.
> Xenoscope: lt-t010726-1: fatal in MvmIrq (time=30000718.974820):
> test interrupted by watchdog.

b) The i386 builds fails in
> /home/buildbot/slave/i386_f/linux-2.6-xenomai/fs/jfs/jfs_metapage.c: In
> function 'metapage_read_end_io':
> /home/buildbot/slave/i386_f/linux-2.6-xenomai/fs/jfs/jfs_metapage.c:295:
> warning: 'return' with a value, in function returning void
> /home/buildbot/slave/i386_f/linux-2.6-xenomai/fs/jfs/jfs_metapage.c: In
> function 'metapage_write_end_io':
> /home/buildbot/slave/i386_f/linux-2.6-xenomai/fs/jfs/jfs_metapage.c:352:
> warning: 'return' with a value, in function returning void CC [M] 
> fs/jfs/jfs_logmgr.o
> /home/buildbot/slave/i386_f/linux-2.6-xenomai/fs/jfs/jfs_logmgr.c: In
> function 'lbmStartIO':
> /home/buildbot/slave/i386_f/linux-2.6-xenomai/fs/jfs/jfs_logmgr.c:2165:
> error: too many arguments to function 'lbmIODone'
> /home/buildbot/slave/i386_f/linux-2.6-xenomai/fs/jfs/jfs_logmgr.c: In
> function 'lbmIODone':
> /home/buildbot/slave/i386_f/linux-2.6-xenomai/fs/jfs/jfs_logmgr.c:2238:
> warning: 'return' with a value, in function returning void
> /home/buildbot/slave/i386_f/linux-2.6-xenomai/fs/jfs/jfs_logmgr.c:2263:
> warning: 'return' with a value, in function returning void
> /home/buildbot/slave/i386_f/linux-2.6-xenomai/fs/jfs/jfs_logmgr.c:2343:
> warning: 'return' with a value, in function returning void make[3]: ***
> [fs/jfs/jfs_logmgr.o] Error 1

c) The buildbot reported the following error for the PPC build in
http://ngiger.dyndns.org/buildbot/builders/ppc_f/builds/1/steps/build/logs/stdio
> /var/buildbot/slave/ppc_f/linux-2.6-xenomai/drivers/net/via-rhine.c:44:1:
> error: unterminated #ifndef make[3]: *** [drivers/net/via-rhine.o] Error 1
> make[2]: *** [drivers/net] Error 2
> make[1]: *** [drivers] Error 2

d) For my PPC405 board I got in
http://ngiger.dyndns.org/buildbot/builders/hcu3_f/builds/2/steps/build/logs/stdio
the error
>   CC      arch/ppc/kernel/smp.o
> /home/buildbot/slave/hcu3_f/linux-2.6-xenomai/arch/ppc/kernel/smp.c: In
> function 'start_secondary':
> /home/buildbot/slave/hcu3_f/linux-2.6-xenomai/arch/ppc/kernel/smp.c:341:
> error: implicit declaration of function 'get_paca'
> /home/buildbot/slave/hcu3_f/linux-2.6-xenomai/arch/ppc/kernel/smp.c:341:
> error: invalid type argument of '->'
> /home/buildbot/slave/hcu3_f/linux-2.6-xenomai/arch/ppc/kernel/smp.c:341:
> warning: cast from pointer to integer of different size make[2]: ***
> [arch/ppc/kernel/smp.o] Error 1
> make[1]: *** [arch/ppc/kernel] Error 2

e) For the TQM (here I am not sure whether I use a good combination of
the Linux tarball, xenomai and rtnet. So please drop me a note to correct
my error. The steps can be found in 
http://ngiger.dyndns.org/buildbot/builders/tqm_f/builds/1
but are distributed. I used the xenomai trunk,
ftp://ftp.denx.de/pub/linux/linuxppc_2_4_devel-2006-04-06-1735.tar.bz2
-adeos=ksrc/arch/powerpc/patches/adeos-ipipe-2.4.25-*.patch 
http://rtnet.svn.sourceforge.net/svnroot/rtnet/trunk/rtnet
To compile the linux kernel I called
make ARCH=ppc uImage modules
with the following environment flags:
  CFLAGS=-g
  CROSS_COMPILE=ppc_8xx-
In
http://ngiger.dyndns.org/buildbot/builders/tqm_f/builds/1/steps/mk_kernel/logs/stdio
you find the following errors:
> In file included from
> /home/buildbot/slave/tqm_f/linux/include/linux/unistd.h:9, from
> init/do_mounts.c:5:
> /home/buildbot/slave/tqm_f/linux/include/asm/unistd.h:385: warning:
> conflicting types for built-in function '_exit' init/do_mounts.c:54: error:
> static declaration of 'root_device_name' follows non-static declaration
> /home/buildbot/slave/tqm_f/linux/include/linux/fs.h:1568: error: previous
> declaration of 'root_device_name' was here init/do_mounts.c: In function
> 'identify_ramdisk_image':
> init/do_mounts.c:507: warning: pointer targets in passing argument 2 of
> 'read' differ in signedness init/do_mounts.c:542: warning: pointer targets
> in passing argument 2 of 'read' differ in signedness init/do_mounts.c: In
> function 'fill_inbuf':
> init/do_mounts.c:1006: warning: pointer targets in passing argument 2 of
> 'read' differ in signedness init/do_mounts.c: In function 'flush_window':
> init/do_mounts.c:1024: warning: pointer targets in passing argument 2 of
> 'write' differ in signedness make: *** [init/do_mounts.o] Error 1

Best regards
-- 
Niklaus Giger
Wieshoschet 6
CH-8753 Mollis
Tel. ++41 55 612 20 54 (privat)
Tel. ++41 55 618 64 68 (Geschäft)

Attachment: make_xenomai.rb
Description: application/ruby

_______________________________________________
Xenomai-core mailing list
Xenomai-core@gna.org
https://mail.gna.org/listinfo/xenomai-core

Reply via email to