www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olivier Lamy <ol...@apache.org>
Subject Re: job failing to archive test reports
Date Fri, 19 Aug 2011 07:36:27 GMT
Hello,
1.413 should have a fix for that (
https://issues.jenkins-ci.org/browse/JENKINS-9017 )

But now upgrading to 1.426 failed (there is a critical issue see
https://issues.jenkins-ci.org/browse/JENKINS-10715 )

You can see this one here : https://builds.apache.org/job/Tuscany-2x/327/console

It should be better to downgrade to 1.425.
The 1.427 should be next week.

2011/8/19 Niklas Gustavsson <niklas@protocol7.com>:
> On Fri, Aug 19, 2011 at 12:40 AM, Andrew Bayer <andrew.bayer@gmail.com> wrote:
>> In my experience, this tends to clear up after killing/restarting the
>> offending slave, but I'm not sure what the underlying problem in Jenkins
>> actually is.
>
> After the last upgrade of Jenkins, we've seen quite a few problems
> with incompatible classes, despite most of our slaves being restarted
> all the time since we take them offline when idle. I'll see if I can
> force an update by removing the slave jars.
>
> /niklas
>



-- 
Olivier Lamy
Talend : http://talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

Mime
View raw message