Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (herse.apache.org: domain of alexey.v.varlamov@gmail.com
 designates 66.249.82.224 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=cI3gE3ZHLKdcgFYp1QUdJNtuRiX3qTrMznXsYJeJn69v8KPYOLdseKCemRwmxMsihRUG4FK5PnXv2zYD6VJmcvLW5buPdDAbJ3/a25rUsyuxsvzbysG/9NptDuI5spvUwOteFvXnetuKs4ObvhxwIFUvwRMXlxa9gZZXjC4dTb4=
Message-ID: <f944d83d0612010042y23acf048lfe7cfdb4ab0d4db9@mail.gmail.com>
Date: Fri, 1 Dec 2006 14:42:00 +0600
From: "Alexey Varlamov" <alexey.v.varlamov@gmail.com>
To: dev@harmony.apache.org
Subject: Re: [DRL VM] classlib tests regressions - could we stop commits to
 DRL VM workspace
In-Reply-To: <906dd82e0612010011h122ac08dn2e5b15ef07959c5b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <6e47b64f0611302109o4e5c9f51k93c50eb2e4dc2745@mail.gmail.com>
	 <906dd82e0611302132k5caa0743v474ead9319162981@mail.gmail.com>
	 <f944d83d0611302145x276d417bgc37f6fe88cb13690@mail.gmail.com>
	 <906dd82e0611302218m2f791b5cu3dd5d162e993201c@mail.gmail.com>
	 <906dd82e0612010011h122ac08dn2e5b15ef07959c5b@mail.gmail.com>

Mikhail,

I believe I found & fixed the root cause, running tests at the moment.

2006/12/1, Mikhail Loenko <mloenko@gmail.com>:
> I've tried "merge -r 480913:480912"
>
> seems like everythung works fine. I'm rerunning the tests...
>
> 2006/12/1, Mikhail Loenko <mloenko@gmail.com>:
> > Isn't waiting less costing? If we roll the changes back we can at least continue
> > further commits. Of course if the reason is clear we should fix it.
> > The problem is
> > that we first broke one test, then one more and then hundreds more. That
> > means that at least several of commits were broken
> >
> > Thanks,
> > Mikhail
> >
> > 2006/12/1, Alexey Varlamov <alexey.v.varlamov@gmail.com>:
> > > Guys,
> > >
> > > Shouldn't rollbacks be the last resort, as it was agreed? Don't you
> > > want to let a chance for primary investigation and hopefully quickfix?
> > > Rollbacks are costly and somewhat demotivating...
> > >
> > > --
> > > Alexey
> > >
> > > 2006/12/1, Mikhail Loenko <mloenko@gmail.com>:
> > > > What is the last working revision? Let's roll back all the
> > > > DRLVM changes since that
> > > >
> > > > 2006/12/1, Stepan Mishura <stepan.mishura@gmail.com>:
> > > > > Hi,
> > > > >
> > > > > Today I see new failures (115) of classlib tests on DRL VM. I didn't see
> > > > > them yesterday . I'm going to find which commit caused regression and roll
> > > > > it back. Could we stop committing new code to DRL VM workspace?
> > > > >
> > > > > Stepan Mishura
> > > > > Intel Enterprise Solutions Software Division
> > > > >
> > > > >
> > > >
> > >
> >
>