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