>>> On 9/1/2008 at 3:35 PM, in message <[EMAIL PROTECTED]>, Carlo Marcelo Arenas Belon <[EMAIL PROTECTED]> wrote: > On Sat, Aug 30, 2008 at 10:09:02AM -0600, Brad Nicholes wrote: >> >>> On 8/30/2008 at 12:25 AM, in message <[EMAIL PROTECTED]>, Carlo >> Marcelo Arenas Belon <[EMAIL PROTECTED]> wrote: >> > On Fri, Aug 29, 2008 at 02:40:00PM -0400, Ofer Inbar wrote: >> >> Should this have made it into 3.1, or 3.1.1? It >> >> doesn't look like it. >> > >> > There is a fix in trunk now with r1738 and unless something goes wrong with >> > it, will be most likely released with 3.1.2 and 3.0.8. > > The proposed backport patch for 3.1.x has been updated in the BUG and > officially requested for inclusion in 3.1 (beware it includes 1 extra > unrelated change that is needed to prevent future conflicts for backporting > but that is otherwise mostly irrelevant, specially if making your own > package) > but also additional changes that simplify the logic and avoid a possible > failure of logic which could result in gmetad crashing, so using this newer > version is encouraged : > > > http://bugzilla.ganglia.info/cgi-bin/bugzilla/attachment.cgi?id=165&action=vi > ew > >> > 3.1.1 is already in testing and since this bug is not a showstopper for > that >> > specific release, I'd be surprised if the release manager decides it should >> > be backported to it, but that shouldn't prevent you patching your own >> > package with the proposed patch if you don't want to wait. >> >> If we are confident enough that the patch for this bug solves the problem > > I am fairly confident that the patch resolves the problem reported in BUG92 > and that matches the description of the problem from Cos, and that is easy > to replicate by just sending a SIGSTOP to gmond; otherwise I wouldn't have > proposed it here, in bugzilla and the STATUS file. > >> then I have no problem scraping 3.1.1, tagging and rolling 3.1.2 and >> restarting the testing period. The whole point of the testing period is >> to flush out problems like this and then determine if the fix is important >> enough to retag and retest. > > agree, but doing so will delay releasing the next version of 3.1 and also > indirectly (as I won't start that until 3.1 is out to avoid confusion and > overstressing our limited testing resources) the next release for 3.0. > > 3.1.1 includes a fix for a showstopper bug (gmetad crash in hierarchical > configuration) and a fix for a high bug (instability with tcpconn.py) which > had been already backported in fedora and gentoo distribution packages, but > not > debian, our own packages or anyone using 3.1 from sources (all other > architectures where there are yet no packages available) and that are > therefore waiting for a 3.1.1 release. > >> We need some feedback on how serious this problem is >
Thanks Carlo, this is some good feedback. I know that both Bernard and Cos have reported having issues with this bug. Could either (or both) of you independently confirm that this patch fixes the problem? Also, is this issue serious enough to stop 3.1.1, add the patch to a 3.1.2 tarball and restart the testing period? Since we are only a week into the current testing cycle, this would delay the release of 3.1.2 by a week (considering a two week testing cycle for 3.1.2). Given the bug fixes that were mentioned by Carlo that have already been included in the 3.1.1 tarball, is a week's delay for 3.1.2 which would include this gmetad patch, worth it? The alternative would be to continue with 3.1.1 as scheduled and have this patch wait for the next release cycle which will probably be at least a couple of months out. I need to know quickly so that we can get moving on a 3.1.2 tarball if that is the consensus. If I don't hear any feedback on this issue by Thurs (9/4), I wil l assume that we are good with 3.1.1 and allow the testing cycle to continue as scheduled. Opinions? Feedback? Comments? Brad ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Ganglia-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general
