You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by Justin Mason <jm...@jmason.org> on 2005/06/02 07:17:36 UTC
Re: 3.1.0 prerelease?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I don't think this is random. I *do* see it in your log though ;)
naturally I'm not seeing that on the other build slaves (or here).
why is it picking up debugs in t/spamd_allow_user_rules.t in the first
place? that test does not use -D.
also, the "server pid" line is what it's waiting for, and as you
can see it never gets to see it. could the machine be very
loaded? or is there a bug in the new Logger code?
I've reordered the "server pid" line to see if that improves
matters.
- --j.
Michael Parker writes:
> Also, I'm randomly getting thiis sort of error in the spamc/spamd tests:
>
> spamd start failed: log: [29808] dbg: logger: adding facilities: all
> [29808] dbg: logger: logging level is DBG
> [29808] dbg: spamd: creating INET socket:
> [29808] dbg: spamd: _Listen: 128
> [29808] dbg: spamd: _LocalAddr: 127.0.0.1
> [29808] dbg: spamd: _LocalPort: 62572
> [29808] dbg: spamd: _Proto: 6
> [29808] dbg: spamd: _ReuseAddr: 1
> [29808] dbg: spamd: _Type: 1
> [29808] dbg: logger: adding facilities: all
> [29808] dbg: logger: logging level is DBG
> lots more debug and then this:
> [29924] info: spamd: server started on port 62688/tcp (running version
> 3.1.0-r179480)
> [29924] info: spamd: server successfully spawned child process, pid 29928
> [29924] dbg: prefork: child 29928: entering state 0
> [29928] dbg: prefork: sysread(7) not ready, wait max 300 secs
> [29924] info: spamd: server successfully spawned child process, pid 29929
> [29924] dbg: prefork: child 29929: entering state 0
> [29929] dbg: prefork: sysread(8) not ready, wait max 300 secs
> [29924] dbg: prefork: child 29928: entering state 1
> [29924] dbg: prefork: child reports idle
> [29924] dbg: prefork: child 29929: entering state 1
> [29924] dbg: prefork: child reports idle
> [29924] info: prefork: child states: II
>
> This leaves a few perl/spamd processes around and other tests fail
> after that.
>
> Michael
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (Darwin)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFCnpLAG4km+uS4gOIRArHbAJ0Wfa8xT+JB85QTHOJT38rDwYCsEQCgqE3p
> sslM8YQ0JTJcIFPyl5YGUVk=VSzT
> -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFCnpZvMJF5cimLx9ARAo0uAKC2Lmce3s7TmqYsl9oArS5M90L92QCghICw
yOHQqiqlngxypxJtywLgIXM=
=ywGE
-----END PGP SIGNATURE-----
Re: 3.1.0 prerelease?
Posted by Michael Parker <pa...@pobox.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael Parker wrote:
> I'll give that one a shot and see how it works.
Ok, everything seems much happier now.
Here is the real question, if there was a problem, why did the tests
still show as passing?
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCnpqzG4km+uS4gOIRAofLAJ9O8E0fnQswjl/1IenIlIdtCyct9QCfa9cS
rezcJRRbmIMYWkig8jhCHlE=
=dyZC
-----END PGP SIGNATURE-----
Re: 3.1.0 prerelease?
Posted by Michael Parker <pa...@pobox.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Justin Mason wrote:
>
> I don't think this is random. I *do* see it in your log though ;)
> naturally I'm not seeing that on the other build slaves (or here).
>
> why is it picking up debugs in t/spamd_allow_user_rules.t in the
> first place? that test does not use -D.
>
One test run it['s in spamd_allow_user_rules, the next spamd_maxsize,
the next spamc_c so on and so forth.
> also, the "server pid" line is what it's waiting for, and as you
> can see it never gets to see it. could the machine be very loaded?
> or is there a bug in the new Logger code?
>
Not terribly loaded, but there might have been a couple of buildbots
running during some of the tests. But I know I've run at least one,
that showed the problem, when nothing else was running on the box.
> I've reordered the "server pid" line to see if that improves
> matters.
>
I'll give that one a shot and see how it works.
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCnpepG4km+uS4gOIRAhvMAJ9MWF0O37PwUAoKtTsnP+Op1vTkbQCcDr15
HxN4H87XuHHzFEQxdz8euSo=
=Smr3
-----END PGP SIGNATURE-----