You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by Apache Jenkins Server <hu...@hudson.apache.org> on 2011/05/05 23:33:49 UTC
Jenkins build is still unstable: SpamAssassin-trunk #6970
See <https://builds.apache.org/hudson/job/SpamAssassin-trunk/changes>
Jenkins build is back to stable : SpamAssassin-trunk #6971
Posted by Apache Jenkins Server <hu...@hudson.apache.org>.
See <https://builds.apache.org/hudson/job/SpamAssassin-trunk/6971/changes>
Re: Jenkins build is still unstable: SpamAssassin-trunk #6970
Posted by Michael Parker <pa...@pobox.com>.
On May 5, 2011, at 7:50 PM, Darxus@ChaosReigns.com wrote:
> On 05/06, Mark Martinec wrote:
>> Thanks, helpful!
>> Worked around it now in Bug 6500 / t/originating_ip_hdr.t
>
> Cool. "make test" and "make disttest" are both passing here now.
>
> Jenkins is quite a lot less self explanatory than it could be.
We can write a custom jelly script that would give us a lot better information. I've attached one that I wrote recently that might be useful for someone with enough access.
Michael
<j:jelly xmlns:j="jelly:core" xmlns:st="jelly:stapler" xmlns:d="jelly:define">
GENERAL INFO
BUILD ${build.result}
Build URL: ${rooturl}/${build.url}
Project: ${project.name}
Date of build: ${it.timestampString}
Build duration: ${build.durationString}
<j:set var="changeSet" value="${build.changeSet}" />
<j:if test="${changeSet!=null}">
<j:whitespace>CHANGE SET </j:whitespace>
<j:set var="hadChanges" value="false"/>
<j:forEach var="cs" items="${changeSet}" varStatus="loop">
<j:set var="hadChanges" value="true"/>
<j:set var="aUser" value="${cs.hudsonUser}"/>
<j:whitespace>Revision ${cs.commitId?:cs.revision?:cs.changeNumber} by ${aUser!=null?aUser.displayName:cs.author.displayName}: (${cs.msgAnnotated}) </j:whitespace>
<j:forEach var="p" items="${cs.affectedFiles}">
<j:whitespace> change: ${p.editType.name} ${p.path} </j:whitespace>
</j:forEach>
</j:forEach>
<j:if test="${!hadChanges}">
<j:whitespace>No changes </j:whitespace>
</j:if>
</j:if>
<!-- JUNIT TEMPLATE -->
<j:set var="junitResultList" value="${it.JUnitTestResult}" />
<j:if test="${junitResultList.isEmpty()!=true}">
Unit Test Results
<j:forEach var="junitResult" items="${it.JUnitTestResult}">
<j:forEach var="packageResult" items="${junitResult.getChildren()}">
Failed: ${packageResult.getFailCount()} test(s), Passed: ${packageResult.getPassCount()} test(s), Skipped: ${packageResult.getSkipCount()} test(s), Total: ${packageResult.getPassCount()+packageResult.getFailCount()+packageResult.getSkipCount()}
Test(s)<j:forEach var="failed_test" items="${packageResult.getFailedTests()}">
Failed: ${failed_test.getFullName()}
${failed_test.getStdout()}
</j:forEach>
</j:forEach>
</j:forEach>
</j:if>
</j:jelly>
Re: Jenkins build is still unstable: SpamAssassin-trunk #6970
Posted by da...@chaosreigns.com.
On 05/06, Mark Martinec wrote:
> Thanks, helpful!
> Worked around it now in Bug 6500 / t/originating_ip_hdr.t
Cool. "make test" and "make disttest" are both passing here now.
Jenkins is quite a lot less self explanatory than it could be.
--
"A ship in a port is safe, but that's not what ships are built for."
-Grace Murray Hopper
http://www.ChaosReigns.com
Re: Jenkins build is still unstable: SpamAssassin-trunk #6970
Posted by Mark Martinec <Ma...@ijs.si>.
Darxus wrote:
> Ah, I guess it's running "make test" then "make disttest", and "make
> disttest" is failing (in trunk):
Thanks, helpful!
Worked around it now in Bug 6500 / t/originating_ip_hdr.t
Mark
Re: Jenkins build is still unstable: SpamAssassin-trunk #6970
Posted by da...@chaosreigns.com.
3.3 is at least failing on the same test. To run just the failing test:
make TEST_FILES=t/originating_ip_hdr.t disttest
Looks like this test was just added for this bug:
clear_originating_ip_headers seems to be broken
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6500
Somebody want to revert related commits until it's figured out?
--
"If the thief is found breaking in, and he is struck so that he dies,
there shall be no guilt for his bloodshed." - Exodus 22:2
http://www.ChaosReigns.com
Re: Jenkins build is still unstable: SpamAssassin-trunk #6970
Posted by da...@chaosreigns.com.
On 05/06, Mark Martinec wrote:
> > > What does that mean? Trunk is passing make test on my Ubuntu Natty box:
> > > All tests successful.
> >
> > So are here. Puzzled...
>
> Why is the t/originating_ip_hdr.t being run twice under Jenkins?
> The first run passes all tests, the second run fails one.
> ???
Ah, I guess it's running "make test" then "make disttest", and "make
disttest" is failing (in trunk):
https://builds.apache.org/hudson/job/SpamAssassin-trunk/6970/testReport/make_disttest/t_originating_ip_hdr_t/test______2/
Checking test_orig_ip_h1
not ok 2
Test Summary Report
-------------------
t/originating_ip_hdr.t (Wstat: 0 Tests: 9 Failed: 1)
Failed test: 2
Files=167, Tests=2080, 164 wallclock secs ( 0.56 usr 0.21 sys + 30.31 cusr 5.54 csys = 36.62 CPU)
Result: FAIL
Failed 1/167 test programs. 1/2080 subtests failed.
make[1]: *** [test_dynamic] Error 255
make[1]: Leaving directory `/home/darxus/masscheckwork/trunk/Mail-SpamAssassin-3.4.0'
make: *** [disttest] Error 2
--
"A ship in a port is safe, but that's not what ships are built for."
-Grace Murray Hopper
http://www.ChaosReigns.com
Re: Jenkins build is still unstable: SpamAssassin-trunk #6970
Posted by Mark Martinec <Ma...@ijs.si>.
> > What does that mean? Trunk is passing make test on my Ubuntu Natty box:
> > All tests successful.
>
> So are here. Puzzled...
Why is the t/originating_ip_hdr.t being run twice under Jenkins?
The first run passes all tests, the second run fails one.
???
Mark
Re: Jenkins build is still unstable: SpamAssassin-trunk #6970
Posted by Mark Martinec <Ma...@ijs.si>.
On Friday May 6 2011 01:00:36 darxus@chaosreigns.com wrote:
> On 05/05, Apache Jenkins Server wrote:
> > See <https://builds.apache.org/hudson/job/SpamAssassin-trunk/changes>
>
> What does that mean? Trunk is passing make test on my Ubuntu Natty box:
>
> All tests successful.
So are here. Puzzled...
Mark
Re: Jenkins build is still unstable: SpamAssassin-trunk #6970
Posted by da...@chaosreigns.com.
On 05/05, Apache Jenkins Server wrote:
> See <https://builds.apache.org/hudson/job/SpamAssassin-trunk/changes>
What does that mean? Trunk is passing make test on my Ubuntu Natty box:
All tests successful.
Files=170, Tests=2144, 345 wallclock secs ( 0.70 usr 0.33 sys + 151.10 cusr 10.79 csys = 162.92 CPU)
Result: PASS
--
"Don't go around saying the world owes you a living. The world owes you
nothing. It was here first." - Mark Twain
http://www.ChaosReigns.com