https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6688
Bug #: 6688
Summary: jenkins fails to build trunk for apparently no good
reason
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: PC
OS/Version: Windows 7
Status: NEW
Severity: normal
Priority: P2
Component: Building & Packaging
AssignedTo: [email protected]
ReportedBy: [email protected]
Classification: Unclassified
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
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
