Bug 6688 - jenkins fails to build trunk for apparently no good reason
Summary: jenkins fails to build trunk for apparently no good reason
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Building & Packaging (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: PC Windows 7
: P2 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-02 14:35 UTC by Kevin A. McGrail
Modified: 2012-03-19 14:29 UTC (History)
1 user (show)


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin A. McGrail 2011-11-02 14:35:16 UTC 
Jenkins appears to have failed3 2x now in the past week 

All three times all we had to do was re-run the build:

<https://builds.apache.org/job/SpamAssassin-trunk/7400/changes> 

This is a test failure where spamd couldn't create a socket. Is this
something in the test routine that needs to be improved because I think
we are spawning spamd on non-standard ports in case a real spamd is running? Is there a good check if the port is used prior to trying to spawn?

Oct 21 10:26:34.901 [36] error: spamd: could not create INET socket on
127.0.0.1:32800: Address already in use
spamd: could not create INET socket on 127.0.0.1:32800: Address already
in use


<https://builds.apache.org/job/SpamAssassin-trunk/7407/changes>

<https://builds.apache.org/job/SpamAssassin-trunk/7425/changes>

7407 and 7425 appear to finish perfectly and then fail "publishing the JUnit test result report"

Perhaps a bug or wonky output in the tap-junit-xml file?

All tests successful.
Files=165, Tests=2083, 179 wallclock secs ( 0.77 usr  0.72 sys + 46.35 cusr 12.83 csys = 60.67 CPU)
Result: PASS
+ mv Mail-SpamAssassin-3.4.0/t/log artifacts/t.log.make_disttest 
+ perl ./build/jenkins/tap-to-junit-xml make test testxml/make_test 
+ perl ./build/jenkins/tap-to-junit-xml make disttest testxml/make_disttest 
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
Recording test results
Build step 'Publish JUnit test result report' changed build result to UNSTABLE

All tests successful.
Files=165, Tests=2083, 206 wallclock secs ( 0.74 usr  0.68 sys + 45.39 cusr 12.59 csys = 59.40 CPU)
Result: PASS
+ mv Mail-SpamAssassin-3.4.0/t/log artifacts/t.log.make_disttest 
+ perl ./build/jenkins/tap-to-junit-xml make test testxml/make_test 
+ perl ./build/jenkins/tap-to-junit-xml make disttest testxml/make_disttest 
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
Recording test results
Build step 'Publish JUnit test result report' changed build result to UNSTABLE
Archiving artifacts
Comment 1 Kevin A. McGrail 2011-11-02 15:05:18 UTC 
I found a link on the Jenkins page:

https://builds.apache.org/job/SpamAssassin-trunk/lastCompletedBuild/testReport/

That showed me more about the error at least for the current build issue:



1..8
# Running under perl version 5.008006 for solaris
# Current time local: Wed Nov  2 13:40:34 2011
# Current time GMT:   Wed Nov  2 13:40:34 2011
# Using Test.pm version 1.25
	/export/home/jm/tools/perl586/bin/perl -T -w ../spamassassin.raw -C log/test_rules_copy  --siteconfigpath log/localrules.tmp -p log/test_default.cf  -L --lint
	Checking anything
ok 1
	/export/home/jm/tools/perl586/bin/perl -T -w ../spamassassin.raw -C log/test_rules_copy  --siteconfigpath log/localrules.tmp -p log/test_default.cf  -L --lint
	Checking anything
ok 2
	/export/home/jm/tools/perl586/bin/perl -T -w ../spamassassin.raw -C log/test_rules_copy  --siteconfigpath log/localrules.tmp -p log/test_default.cf  -L --lint
	Checking anything
ok 3
	/export/home/jm/tools/perl586/bin/perl -T -w ../spamassassin.raw -C log/test_rules_copy  --siteconfigpath log/localrules.tmp -p log/test_default.cf  -L --lint
	Checking anything
ok 4
	/export/home/jm/tools/perl586/bin/perl -T -w ../spamassassin.raw -C log/test_rules_copy  --siteconfigpath log/localrules.tmp -p log/test_default.cf  -L --lint
	Checking anything
ok 5
	/export/home/jm/tools/perl586/bin/perl -T -w ../spamassassin.raw -C log/test_rules_copy  --siteconfigpath log/localrules.tmp -p log/test_default.cf  -L --lint
	Checking anything
ok 6
	/export/home/jm/tools/perl586/bin/perl -T -w ../spamassassin.raw -C log/test_rules_copy  --siteconfigpath log/localrules.tmp -p log/test_default.cf  -L --lint
	Checking anything
ok 7
	/export/home/jm/tools/perl586/bin/perl -T -w ../spamassassin.raw -C log/test_rules_copy  --siteconfigpath log/localrules.tmp -p log/test_default.cf  -L --lint
Nov  2 13:40:59.714 [1797] warn: config: warning: description exists for non-existent rule ADVANCE_FEE_2
Nov  2 13:40:59.875 [1797] warn: config: warning: description exists for non-existent rule ADVANCE_FEE_3
Nov  2 13:40:59.875 [1797] warn: config: warning: description exists for non-existent rule ADVANCE_FEE_4
Nov  2 13:40:59.875 [1797] warn: config: warning: description exists for non-existent rule EXTRA_MPART_TYPE
Nov  2 13:40:59.875 [1797] warn: config: warning: description exists for non-existent rule RATWARE_GECKO_BUILD
Nov  2 13:40:59.875 [1797] warn: config: warning: description exists for non-existent rule ACCESSDB
Nov  2 13:40:59.875 [1797] warn: config: warning: description exists for non-existent rule MICROSOFT_EXECUTABLE
Nov  2 13:40:59.875 [1797] warn: config: warning: description exists for non-existent rule MIME_SUSPECT_NAME
Nov  2 13:40:59.876 [1797] warn: config: warning: description exists for non-existent rule DCC_CHECK
Nov  2 13:40:59.876 [1797] warn: config: warning: description exists for non-existent rule DCC_REPUT_00_12
Nov  2 13:40:59.876 [1797] warn: config: warning: description exists for non-existent rule DCC_REPUT_70_89
Nov  2 13:40:59.876 [1797] warn: config: warning: description exists for non-existent rule DCC_REPUT_90_94
Nov  2 13:40:59.876 [1797] warn: config: warning: description exists for non-existent rule DCC_REPUT_95_98
Nov  2 13:40:59.876 [1797] warn: config: warning: description exists for non-existent rule DCC_REPUT_99_100
Nov  2 13:40:59.876 [1797] warn: config: warning: description exists for non-existent rule UNWANTED_LANGUAGE_BODY
Nov  2 13:40:59.876 [1797] warn: config: warning: description exists for non-existent rule BODY_8BITS
Nov  2 13:40:59.876 [1797] warn: config: warning: description exists for non-existent rule SHORTCIRCUIT
Nov  2 13:41:01.051 [1797] warn: lint: 17 issues detected, please rerun with debug enabled for more information
	Checking anything
not ok 8
	Not found: anything =    at t/lang_lint.t line 23.
# Failed test 8 in t/SATest.pm at line 748
 Failed 1/8 subtests


I can recreate on my devel box with 

perl t/lang_lint.t TEST_VERBOSE=1  


with run_long_tests=y in config.dist (or similar

Looks to be non-existent rules that were described in the new pt_br translation.

svn commit -m 'Changes to pt_br translation to pass perl t/lang_lint.t TEST_VERBOSE=1 with long tests enabled' rules/30_text_pt_br.cf  
Sending        rules/30_text_pt_br.cf
Transmitting file data .
Committed revision 1196617.

So hopefully next time the other errors occur, I can check that link above to maybe discover the issue easier.


The spamd issue is still out there though so this bug should stay open to keep an eye on things.
Comment 2 AXB 2011-11-02 15:27:11 UTC 
lemme guess:  "warning: description exists for non-existent rule" come from the portuguese lang file you checked in yesterday ?
Comment 3 Kevin A. McGrail 2011-11-02 15:40:25 UTC 
(In reply to comment #2)
> lemme guess:  "warning: description exists for non-existent rule" come from the
> portuguese lang file you checked in yesterday ?

No.  I think it was this morning I checked it in ;-)
Comment 4 Kevin A. McGrail 2012-03-19 14:29:12 UTC 
This was resolved some time ago and not updated.