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 2013/01/04 06:21:18 UTC

Jenkins build became unstable: SpamAssassin-trunk #8280

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

Re: Fwd: Jenkins build is still unstable: SpamAssassin-trunk #8283

Posted by Mark Martinec <Ma...@ijs.si>.

Kevin,

> OK, so we are consistently failing this test on Jenkins
> [...]
> But your thinking this is a bug similar to freemail where we have
> incorrect output going into the report?

I think so, but I need to check to make sure.

> Or could it be something DNS related such as rate limiting?

Not likely.

  Mark

Re: Jenkins build is still unstable: SpamAssassin-trunk #8283

Posted by "Kevin A. McGrail" <KM...@PCCC.com>.

On 1/4/2013 12:37 PM, Michael Parker wrote:
> On Jan 4, 2013, at 11:24 AM, Kevin A. McGrail <KM...@PCCC.com> wrote:
>>
>> OK, so we are consistently failing this test on Jenkins
>>
>> https://builds.apache.org/job/SpamAssassin-trunk/8284/testReport/make_test/t_uribl_all_types_t/test______2/
>>
>> And I don't know if we can get the output log.
>>
> One thing you could do is modify the tests/jenkins to archive the logs so that you can go to the web interface and review them.  I'd actually be surprised if that wasn't already done.
>
> It's been awhile since I messed with the source, but I think just adding a tar czvf log_output.tgz WORKDIR/t/log/* or whatever the path actually is, would get you a .tgz of the logs and then modify the Jenkins config to archive that file along with the results.
>
Thanks Michael and Mark,

I'm moving this to a bug because it's blocking the 3.4.0-pre2

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6884

Assuming that this issue is not occurring for any one else on their own systems?

Regards,
KAM

Re: Jenkins build is still unstable: SpamAssassin-trunk #8283

Posted by Michael Parker <pa...@pobox.com>.

On Jan 4, 2013, at 11:24 AM, Kevin A. McGrail <KM...@PCCC.com> wrote:
> 
> 
> OK, so we are consistently failing this test on Jenkins
> 
> https://builds.apache.org/job/SpamAssassin-trunk/8284/testReport/make_test/t_uribl_all_types_t/test______2/
> 
> And I don't know if we can get the output log.
> 

One thing you could do is modify the tests/jenkins to archive the logs so that you can go to the web interface and review them.  I'd actually be surprised if that wasn't already done.

It's been awhile since I messed with the source, but I think just adding a tar czvf log_output.tgz WORKDIR/t/log/* or whatever the path actually is, would get you a .tgz of the logs and then modify the Jenkins config to archive that file along with the results.

Michael

Re: Fwd: Jenkins build is still unstable: SpamAssassin-trunk #8283

Posted by "Kevin A. McGrail" <KM...@PCCC.com>.

On 1/4/2013 12:06 PM, Mark Martinec wrote:
>> Back to the two URIBL tests.
>>
>> https://builds.apache.org/job/SpamAssassin-trunk/8283/testReport/
>>
>> Anyone got a moment to look into this?
> We've ween this before (need to find a ref...).
>
> The additional text on URIBL rules can be wrong (belonging
> to another test). Running the same test more than once
> will give different results:
>
> Correct:
>
>   1.0 X_URIBL_IPSONLY        X_URIBL_IPSONLY
>                              [URIs: 144.137.3.98]
>
>
> Wrong:
>
>   1.0 X_URIBL_IPSONLY        X_URIBL_IPSONLY
>                              [URIs: uribl-example-c.com]
Thanks Mark,

OK, so we are consistently failing this test on Jenkins

https://builds.apache.org/job/SpamAssassin-trunk/8284/testReport/make_test/t_uribl_all_types_t/test______2/

And I don't know if we can get the output log.

But your thinking this is a bug similar to freemail where we have 
incorrect output going into the report?

Or could it be something DNS related such as rate limiting?

Regards,
KAM

Re: Fwd: Jenkins build is still unstable: SpamAssassin-trunk #8283

Posted by Mark Martinec <Ma...@ijs.si>.

> Back to the two URIBL tests.
> 
> https://builds.apache.org/job/SpamAssassin-trunk/8283/testReport/
> 
> Anyone got a moment to look into this?

We've ween this before (need to find a ref...).

The additional text on URIBL rules can be wrong (belonging
to another test). Running the same test more than once
will give different results:

Correct: 

 1.0 X_URIBL_IPSONLY        X_URIBL_IPSONLY
                            [URIs: 144.137.3.98]


Wrong:

 1.0 X_URIBL_IPSONLY        X_URIBL_IPSONLY
                            [URIs: uribl-example-c.com]


Mark