Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (athena.apache.org: domain of alexei.zakharov@gmail.com
 designates 209.85.146.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Fezv3T/2JR0hvlJPz/8y4Unj5Am6DCJiY5TO5MhjwCB6tgrcmKcw0AOcfWVLDaZq2yo3KPVcbxAKECWRrKtX1EFeZRYViBdl55+13mTArmh3R1slt6pkHGvnnO2ClScWoKK96zW1fzRYODwCihxk4m+A3cwCit/BIOSGRLi0iHo=
Message-ID: <2c9597b90711161020v7e5b037ckb947e0e6bd365249@mail.gmail.com>
Date: Fri, 16 Nov 2007 21:20:48 +0300
From: "Alexei Zakharov" <alexei.zakharov@gmail.com>
To: dev@harmony.apache.org
Subject: Re: [testing] Warning: no successful snapshot builds for 2 weeks!
In-Reply-To: <2c9597b90711160642h5defc85s52af2ffdb0f8b75@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <6e47b64f0711160046h659fe4fbm1f06dc563aa4aa51@mail.gmail.com>
	 <2c9597b90711160642h5defc85s52af2ffdb0f8b75@mail.gmail.com>

Issue number 1:
javax.print.attribute.HashAttributeTest failure on Windows32. It fails
only in case if no default printer was defined in system. This issue
was caused by two sequential commits to *print* module:
r593524 Print service implementation (HARMONY-5083)
r594925 Reimplemented getDefaultPrinterName() because the current
implementation uses GetDefaultPrinterW which causes an error on some
systems
I don't want to revert these commits by myself since a lot of useful
code was added. I created HARMONY-5138 and put all details there.
Andrey, as author of above-mentioned commits, could you please take a
look?

Thanks,
Alexei

2007/11/16, Alexei Zakharov <alexei.zakharov@gmail.com>:
> FYI I am working on class library test failures now.
>
> Regards,
> Alexei
>
> 2007/11/16, Stepan Mishura <stepan.mishura@gmail.com>:
> > Hi,
> >
> > Some time ago there was a thread about publishing successful snapshots
> > builds[1].
> > We agreed that successful build is the build which passed:
> > classlib tests, drlvm and drlvm-regression tests, jdktools tests
> > and Eclipse hello world application scenario on Linux/Windows ia32 platform.
> >
> > Also there was suggestion (that I fully support) that if there hasn't
> > been a 'successful' build for more than 2 weeks we should stop and fix
> > it.
> >
> > The last such build was r590919 from Nov 1. According to the integrity
> > testing report we won't have successful build this weekend. Also there
> > is big degradation on Windows 64 bits platform.
> >
> > I think that it make sense to have stabilization period right now. I'd
> > suggest that during this period we shouldn't commit any new
> > functionality or do code redesign. Only bug fixes for current bugs.
> >
> > Objection? Thoughts?
> >
> > [1] http://markmail.org/message/ughx6xj655cchyzg
> >
> > Thanks,
> > Stepan Mishura
> > Intel Enterprise Solutions Software Division
> >
>