You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by Sidney Markowitz <si...@apache.org> on 2010/04/05 19:56:43 UTC
The recent Hudson failure
Apache Hudson Server wrote, On 6/04/10 3:51 AM:
> [locks-and-latches] All the locks released
> FATAL: Timer already cancelled.
> java.lang.IllegalStateException: Timer already cancelled.
> at java.util.Timer.sched(Timer.java:354)
> at java.util.Timer.schedule(Timer.java:170)
> at hudson.plugins.build_timeout.BuildTimeoutWrapper$1EnvironmentImpl.<init>(BuildTimeoutWrapper.java:69)
[ ... etc. ...]
Am I right in thinking that this has to be a problem with the build/test
server and not the result of any of the SpamAssassin checkins? Does
anyone know how to fix this?
-- sidney
Re: The recent Hudson failure
Posted by Justin Mason <jm...@jmason.org>.
On Mon, Apr 5, 2010 at 18:56, Sidney Markowitz <si...@apache.org> wrote:
> Apache Hudson Server wrote, On 6/04/10 3:51 AM:
>> [locks-and-latches] All the locks released
>> FATAL: Timer already cancelled.
>> java.lang.IllegalStateException: Timer already cancelled.
>> at java.util.Timer.sched(Timer.java:354)
>> at java.util.Timer.schedule(Timer.java:170)
>> at hudson.plugins.build_timeout.BuildTimeoutWrapper$1EnvironmentImpl.<init>(BuildTimeoutWrapper.java:69)
> [ ... etc. ...]
>
> Am I right in thinking that this has to be a problem with the build/test
> server and not the result of any of the SpamAssassin checkins? Does
> anyone know how to fix this?
I think this may have been Hudson being shut down -- a mail from Jukka
around the same time indicated that he upgraded Hudson.
Re: The recent Hudson failure
Posted by John Hardin <jh...@impsec.org>.
On Mon, 5 Apr 2010, Adam Katz wrote:
> The unstable result comes from a failed meta test due to a dependency
> error caused by John Hardin's removal of ADVANCE_FEE_2_NEW
Not removal, rather marking something dependant on it as "publish" without
also marking it as "publish" - or doing a test build before committing.
Fixed. Apologies.
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhardin@impsec.org FALaholic #11174 pgpk -a jhardin@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
Homeland Security: Specializing in Tactical Band-aids for Strategic
Problems. -- Eric K. in Bruce Schneier's blog
-----------------------------------------------------------------------
8 days until Thomas Jefferson's 267th Birthday
Re: The recent Hudson failure
Posted by Adam Katz <an...@khopis.com>.
On 04/05/2010 01:56 PM, Sidney Markowitz wrote:
> Am I right in thinking that this has to be a problem with the
> build/test server and not the result of any of the SpamAssassin
> checkins? Does anyone know how to fix this?
That's my thinking, though it looks like it might be resolved as of
build #5250. The first failure, build #5248, only had Justin's
automated sought update (which should be fine due to the automation):
http://hudson.zones.apache.org/hudson/job/SpamAssassin-trunk/5248/
>From #5248's console output, I see this:
> FATAL: command execution failed
> hudson.util.IOException2: Failed to join the process
...
> FATAL: Unable to delete script file
> /var/tmp/hudson6691967404758152626.sh
> hudson.util.IOException2:
> remote file operation failed: /var/tmp/hudson6691967404758152626.sh
> at hudson.remoting.Channel@3eff14:hudson-solaris (Solaris)
...
> [locks-and-latches] Releasing all the locks
> [locks-and-latches] All the locks released
> FATAL: channel is already closed
> hudson.remoting.ChannelClosedException: channel is already closed
This differs from #5249, which dies MUCH sooner:
> At revision 930883
> [locks-and-latches] Checking to see if we really have the locks
> [locks-and-latches] Have all the locks, build can start
> [locks-and-latches] Releasing all the locks
> [locks-and-latches] All the locks released
> FATAL: Timer already cancelled.
> java.lang.IllegalStateException: Timer already cancelled.
These java errors disappear for build #5250, which actually completes
the build and test:
> All tests successful.
> Files=166, Tests=2052, 159 wallclock secs ( 0.67 usr 0.60 sys
> + 40.82 cusr 8.77 csys = 50.86 CPU)
> Result: PASS
> + mv Mail-SpamAssassin-3.4.0/t/log artifacts/t.log.make_disttest
> + perl ./build/hudson/tap-to-junit-xml make test testxml/make_test
> + perl ./build/hudson/tap-to-junit-xml make disttest
> testxml/make_disttest
> [locks-and-latches] Releasing all the locks
> [locks-and-latches] All the locks released
> Archiving artifacts
> Recording test results
> Sending e-mails to: dev@spamassassin.apache.org khopesh@apache.org
> jhardin@apache.org spamassassin_role@apache.org jm@apache.org
> sidney@apache.org
> Finished: UNSTABLE
The unstable result comes from a failed meta test due to a dependency
error caused by John Hardin's removal of ADVANCE_FEE_2_NEW as noted at
http://hudson.zones.apache.org/hudson/job/SpamAssassin-trunk/5250/testReport/make_test/t_basic_meta_t/test______2/
My own test run had one more failure coming from dnsbl_subtests:
> Test Summary Report
> -------------------
> t/basic_meta.t (Wstat: 0 Tests: 2 Failed: 1)
> Failed test: 2
> t/dnsbl_subtests.t (Wstat: 0 Tests: 47 Failed: 30)
> Failed tests: 2-9, 17-25, 31-43
> Files=169, Tests=2123, 527 wallclock secs ( 1.37 usr 0.28 sys
> + 259.42 cusr 16.66 csys = 277.73 CPU)
> Result: FAIL
> Failed 2/169 test programs. 31/2123 subtests failed.
> make: *** [test_dynamic] Error 255
The scrollback (which I've logged if anybody wants it) notes missing
test rules prefixed with X_URIBL_Y*.