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 <[EMAIL PROTECTED]>: > > Hi Vladimir, > > On 10/1/07, Vladimir Beliaev <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]>: > > > > > > 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 <[EMAIL PROTECTED]>: > > > > > > > > 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 < [EMAIL PROTECTED]>: > > > > > > > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Vladimir Beliaev > > > > > Intel Middleware Products Division > > > > > > > > > > > > > > > > -- > > > Vladimir Beliaev > > > Intel Middleware Products Division > > > > > > > > > > > -- > > Vladimir Beliaev > > Intel Middleware Products Division > > > -- Vladimir Beliaev Intel Middleware Products Division
