Xenofarm does no intentional blacklisting, but there is a bug or eight when it comes to handling broken result packages and similar, that has the effect of discriminating some machines, just the same. If possible and given the incitament and time we try to work them out and improve on the system, and welcome the help from motivated people too. :-)

Good places to peek are /pike/data/pikefarm/ (at pike.ida.liu.se), and reviewing the logs in /pike/home/xenofarm/ and we try to keep xenofarm as documented as possible (at http://www.lysator.liu.se/xenofarm/ or, even more likely to be up to date, in the xenofarm repository itself, http://www.lysator.liu.se/codelibrarian/browse.xml?module=xenofarm or CVS_ROOT=:pserver:anonymous@cvs.lysator.liu.se:/cvsroot/xenofarm cvs co xenofarm).

Ideally some of us who set it up will get busy finding and fixing the problems we hear about, but it's surprising how often we can not. :-] Having others participate, peek at and care for valuable systems like xenofarm might be a good idea.

/ Johan Sundström (Achtung Liebe!)

Previous text:

2004-05-26 14:50: Subject: OpenBSD and pike...

---

Hello,

According to http://pike.ida.liu.se/generated/pikefarm/7.7/97_28/verifylog.txt

We have : Doing tests in modules/files/testsuite (94 tests) 0: ++++++++++ ++++++++++ ++++++++++ ++++++++++ ++++++++++ 50: ++++++++++ ++++++++++ ++++++++++ +++--+++++ Available fds: 1024

Forking... ok. Doing simple tests. Testing dup & assign. / Testing accept. -\|/-\| Testing uni-directional shutdown on socket Testing uni-directional shutdown on pipe Testing 12 sockets. /-\| Testing 16 sockets. /-\| Testing 20 sockets. /-\|/- Testing 24 sockets. \|/-\| Testing 28 sockets. /-\|/-\| Testing 32 sockets. /-\|/-\| Testing 36 sockets. /-\|/-\|/- Testing 40 sockets. \|/-\|/-\| Testing 44 sockets. /-\|/-\|/-\| Testing 48 sockets. /-\Accept returned 0, errno: 9 64 open fds: 0 - 63

[WATCHDOG] Pike testsuite timeout, sending SIGABRT. Abort (core dumped) *** Error code 134

Gdb says (http://pike.ida.liu.se/generated/pikefarm/7.7/97_28/core.txt) :

Core was generated by `pike'. Program terminated with signal 6, Abort trap. #0 0x12793dd in poll ()

Active threads

Backtrace #0 0x12793dd in poll () #1 0x7ddfda0 in _thread_kern_poll () #2 0x7ddf746 in _thread_kern_sched () #3 0x7ddf971 in _thread_kern_sched_state () #4 0x7dd9d73 in poll () #5 0x1c112353 in handle_timeouts (ignored=0x0) at /usr/home/kiwi/xenoclient/pike-7.7/obsd.home.oav.net/buildtmp/Pike- v7.7-snapshot/src/modules/HTTPLoop/timeout.c:192 #6 0x7dd703d in _thread_start () #7 0x1f in ?? () Cannot access memory at address 0xffffffff.

This bug is here for ages... for both pike 7.6 and 7.7 (I don't have pike 7.4 on xenofarm even my box is sending data... so I cannot compare... do xenofarm does some "blacklisting ????")..

Can I help to fix that ?

/Xavier

-- Xavier Beaudouin - Unix System Administrator & Projects Leader. President of Kazar Organization : http://www.kazar.net/ Please visit http://caudium.net/, home of Caudium & Camas projects

/ Brevbäraren

I don't know why it doesn't show up; it's listed in the result parser log:

[11:19:35] Found new result "/pike/data/pikefarm/in/7.4/res1090401529_2.tar.gz" [11:19:35] Build: 575 Host: "rubis.anima-agency.net" Platform: "Linux 2.2.20 alpha" [12:45:45] Found new result "/pike/data/pikefarm/in/7.4/res1090493117_3.tar.gz" [12:45:45] Build: 575 Host: "E-T.linkeo.intra" Platform: "Darwin 7.4.0 Power Macintosh" [14:16:46] Found new result "/pike/data/pikefarm/in/7.4/res1090498547_4.tar.gz" [14:16:47] Build: 575 Host: "rubis.anima.net" Platform: "Linux 2.2.20 alpha"

(Both rubis.anima-agency.net and rubis.anima.net show up properly).

/ Henrik Grubbström (Lysator)

Previous text:

2004-07-22 14:59: Subject: Omited pikefarm results (was: Re: OpenBSD and pike...)

---

...

Xenofarm does no intentional blacklisting, but there is a bug or eight when it comes to handling broken result packages and similar, that has the effect of discriminating some machines, just the same. If possible and given the incitament and time we try to work them out and improve on the system, and welcome the help from motivated people too. :-)

Good places to peek are /pike/data/pikefarm/ (at pike.ida.liu.se), and reviewing the logs in /pike/home/xenofarm/

What is the status of this? Is there still other people whose pikefarm results don't appear on the website?

I sent some (7.4, 7.6, 7.7) today with a darwin 7.4.0 machine (E-T.linkeo.intra) which don't shows up in the list, if this can help to track down the bug.

-- Bertrand

récursion: nm Voir récursion.

/ Brevbäraren

In the last episode (Jul 22), Bertrand LUPART said:

Is Darwin 7.x the only platform affected? I don't see any OpenBSD nor Cygwin clients in the result pages.

Cygwin builds successfully submitted results the last time I checked (around October). I stopped running them because they would occasionally lock up the machine, and I'd rather use a native win32 pike anyway.