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 vladimir.k.beliaev@gmail.com
 designates 64.233.166.181 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:references;
        b=Jqg6NtwBHzSx3keL6Bj4T5224fpSHvFK9TpWmDSxN9qzj9+8TG8zO8cH4ZkhIFD3fcQMCl77D+BAk5tpYfbyhDTeah+OS/uQgJz3ftjbI4iQwOcyGvYibNPhuhKGPftKmNDokTOWLax0p42MAseP/wQz5GFYW8NsFq5mHzkQM8Q=
Message-ID: <587698b80710010409x7a6c5bd6rad02e168a2edee2d@mail.gmail.com>
Date: Mon, 1 Oct 2007 15:09:29 +0400
From: "Vladimir Beliaev" <vladimir.k.beliaev@gmail.com>
To: dev@harmony.apache.org
Subject: Re: [buildtest][eut] set of EUT patches for M3 to be integrated
In-Reply-To: <587698b80710010331s3873313fxb57d20b0d16dc71a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_9993_33002796.1191236969365"
References: <587698b80709250459n619138dfje28b77d1404c1b05@mail.gmail.com>
	 <6e47b64f0709250848r1c37eba0yf0128c3bbe6610e7@mail.gmail.com>
	 <587698b80709260103p21a96e5bm3925d6881d61ef96@mail.gmail.com>
	 <587698b80710010224m5aed076ey69d25109cd32e2d2@mail.gmail.com>
	 <6e47b64f0710010313i636c1109u33ed775943a64b53@mail.gmail.com>
	 <587698b80710010331s3873313fxb57d20b0d16dc71a@mail.gmail.com>

------=_Part_9993_33002796.1191236969365
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

BTW, I complete testing the failures/errors/crashes I've got locally during
nightly run.

They are NOT reproducible if I run a single EUT Suite (like jdtdebug or
jdttext).

So the EFL patches you just committed are to produce the corrct EFLs (or
these local issues are intermittent ones).

So, let's see what your cycled testing will show.

Thanks
Vladimir Beliaev

2007/10/1, Vladimir Beliaev <vladimir.k.beliaev@gmail.com>:
>
> I agree about 5-7 times. Still there are two ways to implement it:
>
> 1. run EUT on daily base, see the results & update EFL (prepare patch &
> commit). Stop doing this when a GREEN picture is table during 2-3 days.
>
> 2. run EUT 1 time with 5-7 cycles which take 8*7=56h=~days. Then work on
> all unexpected failures / error. I'm ok with such a variant also (it less
> timeconsuming for us).
>
> So please choose what is simpler for you to implement. I believe, the
> regualr testing of new M3 snapshot willl be done in parallel.
>
> Thanks
> Vladimir Beliaev
>
>
> 2007/10/1, Stepan Mishura <stepan.mishura@gmail.com>:
> >
> > Hi Vladimir,
> >
> > On 10/1/07, Vladimir Beliaev <vladimir.k.beliaev@gmail.com > wrote:
> > > Hello, Stepan,
> > >
> > > please get committed the patches for EFL updating which are:
> > >
> > >   - HARMONY-4870 <https://issues.apache.org/jira/browse/HARMONY-4870 >
> > > ([buildtest][eut]
> > >   fixed EFL for EUT3.2)
> > >   - HARMONY-4871 <https://issues.apache.org/jira/browse/HARMONY-4871>
> > > ([buildtest][eut]
> > >   fixed EFL for EUT3.3)
> > >   - HARMONY-4878 <https://issues.apache.org/jira/browse/HARMONY-4878>
> > > ([buildtest][eut]
> > >   copy EFL to report on people.apache.org)
> > >
> >
> > done.
> >
> > >  Pleas note that ... more changes on EFL may be done since there may
> > be
> > > intermittent failures.
> > >
> > > I recommend establishing a daily run of EUT ( 3.2/3.3 x winx86/linx86)
> > on
> > > same snapshot - M3 - to be able to define the list of tests which are
> > > fixedly passed each run.
> > >
> >
> > Why daily? If we want to catch all intermittent failures for M3 may be
> > it is better to run tests several times (5-7?) on the snapshot.
> >
> > Thanks,
> > Stepan.
> >
> > > Thanks
> > > Vladimir Beliaev
> > > 2007/9/26, Vladimir Beliaev < vladimir.k.beliaev@gmail.com>:
> > > >
> > > > Thanks, Stepan.
> > > >
> > > > >> 3. HARMONY-4849
> > > > >> <https://issues.apache.org/jira/browse/HARMONY-4849
> > >([buildtest][eut]
> > > > >> warn if passed test is in EFL)
> > > > >>
> > > > >
> > > > > Looking
> > > >
> > > > It seems to be simple - just System.err.println() with warning :)
> > > >
> > > > Thanks
> > > > Vladimir Beliaev
> > > >
> > > > 2007/9/25, Stepan Mishura <stepan.mishura@gmail.com>:
> > > > >
> > > > > On 9/25/07, Vladimir Beliaev wrote:
> > > > > > Hello, Stepan,
> > > > > >
> > > > > > The EUT status on M3 is red (although there is no bug fixing
> > remained
> > > > > for
> > > > > > M3). To make it GREEN let's get several actions done:
> > > > > >
> > > > > > a) fix Summary Reporter to consider Expected Crashes
> > > > > >
> > > > > > b) correct Expected Failure List files for particular EUT
> > version /
> > > > > platform
> > > > > >
> > > > > > For now I propose to commit set of patches related to EUT
> > CC-based
> > > > > automated
> > > > > > testing. Here they are:
> > > > > >
> > > > > > 1. HARMONY-4835 ([buildtest][eut] Expected Crashes must be
> > considered
> > > > > by
> > > > > > summary reporter)
> > > > > >
> > > > >
> > > > > Done.
> > > > >
> > > > > > 2. HARMONY-4847 ([buildtest][eut] rename index.htm to index.htmland
> > > > > add
> > > > > > links to output.txt and report.txt)
> > > > > >
> > > > >
> > > > > Done.
> > > > >
> > > > > > 3. HARMONY-4849
> > > > > > < https://issues.apache.org/jira/browse/HARMONY-4849
> > >([buildtest][eut]
> > > > > > warn if passed test is in EFL)
> > > > > >
> > > > >
> > > > > Looking
> > > > >
> > > > > -Stepan.
> > > > >
> > > > > > *Please get them committed before next snapshot testing*.
> > > > > >
> > > > > > I still need to prepare some EFL-related patches to be proposed
> > for
> > > > > M3.
> > > > > >
> > > > > > Thanks
> > > > > > Vladimir Beliaev
> > > > > >
> > > > > > 2007/9/22, Stepan Mishura < stepan.mishura@gmail.com>:
> > > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > According to the plan - Sept. 22 is code freeze date for M3 so
> > let's
> > > > > > > follow policy:
> > > > > > > "no more commits please without agreement from two committers
> > on the
> > > > > dev
> > > > > > > list."
> > > > > > >
> > > > > > > Let's do more testing and analyze if there any
> > critical/blocker
> > > > > issues
> > > > > > > for consideration.
> > > > > > > Please raise here issues that you think MUST be fixed for M3.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Stepan Mishura
> > > > > > > Intel Enterprise Solutions Software Division
>
>

------=_Part_9993_33002796.1191236969365--