From continuum-users-return-4711-apmail-maven-continuum-users-archive=maven.apache.org@maven.apache.org Fri Sep 21 14:03:34 2007 Return-Path: Delivered-To: apmail-maven-continuum-users-archive@www.apache.org Received: (qmail 93919 invoked from network); 21 Sep 2007 14:03:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Sep 2007 14:03:33 -0000 Received: (qmail 84032 invoked by uid 500); 21 Sep 2007 14:03:23 -0000 Delivered-To: apmail-maven-continuum-users-archive@maven.apache.org Received: (qmail 84009 invoked by uid 500); 21 Sep 2007 14:03:23 -0000 Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: continuum-users@maven.apache.org Delivered-To: mailing list continuum-users@maven.apache.org Received: (qmail 83998 invoked by uid 99); 21 Sep 2007 14:03:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Sep 2007 07:03:23 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [80.168.101.19] (HELO relay01-mail.uk.clara.net) (80.168.101.19) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Sep 2007 14:03:20 +0000 Received: from chb28-2-88-163-39-128.fbx.proxad.net ([88.163.39.128]:4363 helo=[127.0.0.1]) by relay01-mail.uk.clara.net (smtp-vh.amenworld.com [195.8.80.31]:251) with esmtpa (authdaemon_plain:emmanuel@venisse.net) id 1IYj5u-0003YQ-3W (Exim 4.60) for continuum-users@maven.apache.org (return-path ); Fri, 21 Sep 2007 14:02:58 +0000 Message-ID: <46F3CED9.8000600@venisse.net> Date: Fri, 21 Sep 2007 16:02:01 +0200 From: Emmanuel Venisse User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: continuum-users@maven.apache.org Subject: Re: the last build is successful but the project shows as "build in error" References: <646056.88713.qm@web36515.mail.mud.yahoo.com> <20070830112324.GE4767@mars.cry.pto> <46D6ABC6.6050907@venisse.net> <20070830120423.GF4767@mars.cry.pto> <46D6BA28.2030504@venisse.net> <20070921124443.GJ29940@mars.cry.pto> <46F3C393.2030307@venisse.net> <20070921133413.GK29940@mars.cry.pto> <46F3CA41.2030206@venisse.net> <20070921135602.GL29940@mars.cry.pto> In-Reply-To: <20070921135602.GL29940@mars.cry.pto> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Julien Stern a écrit : > On Fri, Sep 21, 2007 at 03:42:25PM +0200, Emmanuel Venisse wrote: >> you use the 1.1-beta-3 sent to the vote, right? not a previeous snapshot? > > Dooh, my bad. I mixed up the numbers. Please replace beta-3 by beta-2 > below. I was originally using beta-1 when I reported the issue, then > upgraded to beta-2. You guys are releasing faster than I can upgrade ;) hehe > > I can try to test beta-3 but as the bug only happens about once a week > now, it will take about two weeks to be confident that it is gone for > good. > > Is there a place where I can download it or should I build it from SVN ? The thread about the release vote and links to download it is there: http://mail-archives.apache.org/mod_mbox/maven-continuum-dev/200709.mbox/%3c46F170AD.9070701@venisse.net%3e > >> I'll try to reproduce it a new time :( > > Don't bother yet. Give me a couple of weeks to try beta-3. > I'll ring you back if the issue it still present. Maybe 1.1 final will be released ;) Emmanuel > > -- > Julien > >> Emmanuel >> >> Julien Stern a écrit : >>> On Fri, Sep 21, 2007 at 03:13:55PM +0200, Emmanuel Venisse wrote: >>>> I fixed it 3 days ago, before to start the vote of 1.1-beta-3 release. >>> Yes, I saw that. It took me some time to actually test beta-3. >>> I originally though the bug was fixed too, as it did not happen >>> for 4 or 5 days. It really seem to happen rarely now. >>> >>> What is mostly annoying with this bug is when it happens on a "stable" >>> project, or worse on a "parent pom". Because the project needs to >>> be rebuilt manually, it forces the rebuild of many projects. >>> >>> What is really weird is that you could not reproduce the bug even >>> with very short schedule. Maybe the fact that we are using CVS >>> (and not SVN) as the SCM could be the difference ? >>> >>>> For 1.1-beta-3, do you use a db from 1.1-beta-2, a new db or a db created >>>> by the migration tool? >>> A new DB. >>> >>> -- >>> Julien >>> >>>> Emmanuel >>>> >>>> Julien Stern a écrit : >>>>> Emmanuel, >>>>> >>>>> just to let you know, that unfortunately, the issue >>>>> http://jira.codehaus.org/browse/CONTINUUM-1384 >>>>> still happens with beta-3, albeit much less often than with beta-2. >>>>> >>>>> It happened twice in the last two weeks. >>>>> In both cases there was nothing in the logs except the fact that >>>>> the cvs update for the failing project and the schedule activator >>>>> were essentially triggered at the same time. >>>>> >>>>> -- >>>>> Julien >>>>> >>>>> On Thu, Aug 30, 2007 at 02:38:00PM +0200, Emmanuel Venisse wrote: >>>>>> Julien Stern a écrit : >>>>>>> On Thu, Aug 30, 2007 at 01:36:38PM +0200, Emmanuel Venisse wrote: >>>>>>>> Julien Stern a écrit : >>>>>>>>> On Thu, Aug 30, 2007 at 03:23:13AM -0700, Ionut S wrote: >>>>>>>>>> Hi, >>>>>>>>>> I don't know for what reason one of our projects (shown when you >>>>>>>>>> hit "Show projects" link) show as "Build in error" although the >>>>>>>>>> last 10 or so builds are successful. >>>>>>>>>> >>>>>>>>>> Did anybody had this problem ? >>>>>>>>> Yes, this happens to us about twice a day with 1.1 >>>>>>>>> It may be related to http://jira.codehaus.org/browse/CONTINUUM-1384 >>>>>>>>> >>>>>>>>> You may want to check your logs to see if this is the same issue >>>>>>>>> or a different one. >>>>>>> Emmanuel, >>>>>>> >>>>>>>> Do you have it with beta-2 too? >>>>>>> sorry, I haven't installed beta-2 yet. I will install it and let >>>>>>> you know. >>>>>>> >>>>>>>> What is your default schedule? >>>>>>> Our default schedule is short (15 minutes) with many projects (> 200). >>>>>>> That's probably why we trigger this issue often. >>>>>> yes. >>>>>> >>>>>>>> What is the max path length for your files? >>>>>>> I'm not sure I understand this question. >>>>>>> If you mean the max length of the absolute unix file path from the cvs >>>>>>> root, I'd hazard a guess as between 128 and 256. >>>>>> it's what I meant. >>>>>> >>>>>>> I've taken a very quick look at the continuum code. I would tend to >>>>>>> think that this issue may be related to a project state that is not >>>>>>> set back >>>>>>> to the correct value because two concurrent threads try to modify it >>>>>>> (the thread that performs the scm update and the thread that queues the >>>>>>> builds ?) >>>>>>> >>>>>>> Maybe (just maybe, really :) ) in the class >>>>>>> UpdateWorkingDirectoryFromScmContinuumAction.java the latest >>>>>>> store.updateProject( project ) could fail, leaving an inconsistent >>>>>>> state ? >>>>>> if the problem always exist in beta-2, yes, it should be the right >>>>>> place to fix it. >>>>>> >>>>>>> Again, this is a wild guess that could be totally wrong, the continuum >>>>>>> code is too complex to be understood after a quick look. >>>>>> The code isn't too complex as you find where we can have an error about >>>>>> project state ;) >>>>>> >>>>>> Emmanuel >>>>>> >>>>>> >>> > >