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 <je...@builds.apache.org> on 2012/09/14 11:10:54 UTC
Jenkins build became unstable: SpamAssassin-trunk #8006
See <https://builds.apache.org/job/SpamAssassin-trunk/8006/changes>
Re: Jenkins build became unstable: SpamAssassin-trunk #8006
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 9/14/2012 9:49 AM, Axb wrote:
> FTR: make test passed on my local system (with no AV)
Thanks and I figured it did. Just being thorough before I involve Infra.
regards,
KAM
Re: Jenkins build became unstable: SpamAssassin-trunk #8006
Posted by Axb <ax...@gmail.com>.
On 09/14/2012 03:47 PM, Kevin A. McGrail wrote:
> On 9/14/2012 5:30 AM, Axb wrote:
>> On 09/14/2012 11:10 AM, Apache Jenkins Server wrote:
>>> See <https://builds.apache.org/job/SpamAssassin-trunk/8006/changes>
>>>
>>
>> Unhappy spamd?
>>
>> https://builds.apache.org/job/SpamAssassin-trunk/8006/testReport/
> Never seen it break like this. Seems to blow up when the GTUBE tests
> are done.
>
> I've reviewed your two commits and they don't really seem related from a
> cursory review. So I'm checking make test on my system to check
> locally. Then I will try another build with jenkins if it passes
> locally. Then I figure we'll need to ask infra if they perhaps have
> added anti-virus software to the server that might be killing things...
FTR: make test passed on my local system (with no AV)
Re: Jenkins build became unstable: SpamAssassin-trunk #8006
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 9/14/2012 5:30 AM, Axb wrote:
> On 09/14/2012 11:10 AM, Apache Jenkins Server wrote:
>> See <https://builds.apache.org/job/SpamAssassin-trunk/8006/changes>
>>
>
> Unhappy spamd?
>
> https://builds.apache.org/job/SpamAssassin-trunk/8006/testReport/
Never seen it break like this. Seems to blow up when the GTUBE tests
are done.
I've reviewed your two commits and they don't really seem related from a
cursory review. So I'm checking make test on my system to check
locally. Then I will try another build with jenkins if it passes
locally. Then I figure we'll need to ask infra if they perhaps have
added anti-virus software to the server that might be killing things...
regards,
KAM
Re: Jenkins build became unstable: SpamAssassin-trunk #8006
Posted by Axb <ax...@gmail.com>.
On 09/14/2012 11:10 AM, Apache Jenkins Server wrote:
> See <https://builds.apache.org/job/SpamAssassin-trunk/8006/changes>
>
Unhappy spamd?
https://builds.apache.org/job/SpamAssassin-trunk/8006/testReport/
Fwd: Jenkins build is back to stable : SpamAssassin-trunk #8008
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
No rhyme or reason why. It's not something programmatic so safely ignore
the build failures.
Regards,
KAM
-------- Original Message --------
Subject: Jenkins build is back to stable : SpamAssassin-trunk #8008
Date: Fri, 14 Sep 2012 15:39:01 +0000 (UTC)
From: Apache Jenkins Server <je...@builds.apache.org>
To: dev@spamassassin.apache.org
See <https://builds.apache.org/job/SpamAssassin-trunk/8008/>
Jenkins build is back to stable : SpamAssassin-trunk #8008
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/SpamAssassin-trunk/8008/>
Jenkins build is still unstable: SpamAssassin-trunk #8007
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/SpamAssassin-trunk/changes>