From dev-return-102939-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org Wed Aug 10 22:03:37 2011 Return-Path: X-Original-To: apmail-cocoon-dev-archive@www.apache.org Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A59E88A72 for ; Wed, 10 Aug 2011 22:03:37 +0000 (UTC) Received: (qmail 11126 invoked by uid 500); 10 Aug 2011 22:03:37 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 11007 invoked by uid 500); 10 Aug 2011 22:03:35 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 10550 invoked by uid 99); 10 Aug 2011 22:03:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Aug 2011 22:03:35 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [88.198.46.98] (HELO indoqa.com) (88.198.46.98) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Aug 2011 22:03:27 +0000 Received: from [192.168.0.132] (chello062178214195.10.15.vie.surfer.at [62.178.214.195]) by indoqa.com (Postfix) with ESMTP id 9BF5D257EEF for ; Thu, 11 Aug 2011 00:03:06 +0200 (CEST) Message-ID: <4E43002A.4020501@indoqa.com> Date: Thu, 11 Aug 2011 00:03:22 +0200 From: Steven Dolg User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Fwd: Cocoon-trunk - Build # 49 - Unstable References: <1665070934.35501313011346450.JavaMail.hudson@aegis> In-Reply-To: <1665070934.35501313011346450.JavaMail.hudson@aegis> X-Forwarded-Message-Id: <1665070934.35501313011346450.JavaMail.hudson@aegis> Content-Type: multipart/alternative; boundary="------------000503060000080107050500" X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. --------------000503060000080107050500 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Oops!... I did it again But this time I'm innocent :P It took me some time to figure this one out since I didn't touch anything near it. My theory is this: With COCOON3-69 ehcache was upgraded from 1.6.1 to 2.4.3. Between those versions, the serialVersionUID of net.sf.ehcache.Element changed, so serialized versions of that class cannot be loaded any more. The build fails because the ehcache for cocoon-profiling is configured to be "diskPersistent" and reading the old cache with the new class fails. The build fails only sometimes, because it fails only once on each node in the build cluster, after that the cache is rewritten with the newer version. Should we wait until the build has spread through all nodes and stopped failing from this or try something else? I'm really for changing the profiling cache to non-persistent - unless that breaks something. Do we need to preserve profiling results between restarts? Cheers, Steven -------- Original-Nachricht -------- Betreff: Cocoon-trunk - Build # 49 - Unstable Datum: Wed, 10 Aug 2011 21:22:17 +0000 (UTC) Von: Apache Jenkins Server An: steven.dolg@indoqa.com The Apache Jenkins build system has built Cocoon-trunk (build #49) Status: Unstable Check console output at https://builds.apache.org/job/Cocoon-trunk/49/ to view the results. --------------000503060000080107050500 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Oops!... I did it again
But this time I'm innocent :P

It took me some time to figure this one out since I didn't touch anything near it.

My theory is this:
With COCOON3-69 ehcache was upgraded from 1.6.1 to 2.4.3.
Between those versions, the serialVersionUID of net.sf.ehcache.Element changed, so serialized versions of that class cannot be loaded any more.

The build fails because the ehcache for cocoon-profiling is configured to be "diskPersistent" and reading the old cache with the new class fails.
The build fails only sometimes, because it fails only once on each node in the build cluster, after that the cache is rewritten with the newer version.

Should we wait until the build has spread through all nodes and stopped failing from this or try something else?
I'm really for changing the profiling cache to non-persistent - unless that breaks something.
Do we need to preserve profiling results between restarts?


Cheers,
Steven

-------- Original-Nachricht --------
Betreff: Cocoon-trunk - Build # 49 - Unstable
Datum: Wed, 10 Aug 2011 21:22:17 +0000 (UTC)
Von: Apache Jenkins Server <jenkins@builds.apache.org>
An: steven.dolg@indoqa.com


The Apache Jenkins build system has built Cocoon-trunk (build #49)

Status: Unstable

Check console output at https://builds.apache.org/job/Cocoon-trunk/49/ to view the results.
--------------000503060000080107050500--