Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (athena.apache.org: domain of jgawor@gmail.com designates
 209.85.210.174 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=tXSC5Frg3xemBD1tQCYP0WZwBMxOERzNt0NOVopjl4KwJMz00/eWi6fHFlyx1IDZhZ
         EyZ6hWGeC+qRX1m0afwvFo5HCGbR/GsNOjpbqtjV8oMhP0ySlApGMwbsyOupsxMtDIX7
         MMmMOmpYVbTggCTSM1vq9ToI3M/iN+t5eoa8I=
MIME-Version: 1.0
In-Reply-To: <f2af330e0907070038o533adf4fm14089a9c05ef95bb@mail.gmail.com>
References: <24B8EAF6-32F9-45EB-B5AA-6F9F2F656948@gmail.com>
	 <5eb405c70906250858o4049aa97xf8e52aab7a77d343@mail.gmail.com>
	 <f2af330e0907011831j2ee000fbjef2ea5088b9dcb7f@mail.gmail.com>
	 <5eb405c70907021153q7edc50acie240326d370fa4e6@mail.gmail.com>
	 <f2af330e0907030753r47681811vc104191125954506@mail.gmail.com>
	 <5eb405c70907061009m60131c17k57bb7dacf4c6efc2@mail.gmail.com>
	 <f2af330e0907070038o533adf4fm14089a9c05ef95bb@mail.gmail.com>
Date: Tue, 7 Jul 2009 11:04:55 -0400
Message-ID: <5eb405c70907070804kfb06381s832bb643ac061bd8@mail.gmail.com>
Subject: Re: Trunk Builds
From: Jarek Gawor <jgawor@gmail.com>
To: dev@geronimo.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Shawn,

Looks like my copy of dojo-release-1.1.1-mini.zip was outdated and
files were wrapped in an extra "dojo" directory. Once I updated it the
extra "dojo" directory disappeared. I updated the DOJO_BASE in
ConfirmMessageTag.java.

Thanks,
Jarek

On Tue, Jul 7, 2009 at 3:38 AM, Shawn Jiang<genspring@gmail.com> wrote:
> Sorry, Are we using the same trunk build ? I downloaded the tomcat trunk
> build here:
>
> http://people.apache.org/builds/geronimo/server/binaries/trunk/20090703/g=
eronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
>
> When accessing=A0 http://localhost:8080/dojo/dojo/dojo.js ,=A0 I got it's
> content:
>
> /*
> 	Copyright (c) 2004-2008, The Dojo Foundation All Rights Reserved.
>
> 	Available via Academic Free License >=3D 2.1 OR the modified BSD license=
.
> 	see: http://dojotoolkit.org/license for details
> */
>
> (function(){var _1=3Dnull;if((_1||(typeof
> djConfig!=3D"undefined"&&djConfig.scopeMap))&&(typeo
>
> When accessing http://localhost:8080/dojo/dojo/dojo/dojo.js, I got this:
>
> HTTP Status 404
>
> I also tried to revert ConfirmMessageTag.java to dojo/dojo/dojo.js from
> dojo/dojo/dojo/dojo.js.=A0=A0 The dialog poped up and the test suite pass=
ed.
> So , can anyone else help verify this ?
>
> On Tue, Jul 7, 2009 at 1:09 AM, Jarek Gawor <jgawor@gmail.com> wrote:
>>
>> Shawn,
>>
>> I recently modified ConfirmMessageTag.java so that it points to the
>> right locations for dojo resources. It used to point to
>> http://localhost:8080/dojo/dojo/dojo.js (which does not work) but now
>> points to http://localhost:8080/dojo/dojo/dojo/dojo.js (which does
>> work). That made the confirmation box to display again. The
>> confirmation box does display now when you use the web browser and
>> follow the steps of the test but somehow it fails in our automatic
>> tests. The test does pass for me when I execute it on my machine in
>> the same way as the automatic tests do... so that's why I thought it
>> was a timing issue. But there might be something else going on, I'm
>> not sure.
>>
>> Jarek
>>
>> On Fri, Jul 3, 2009 at 10:53 AM, Shawn Jiang<genspring@gmail.com> wrote:
>> >
>> >
>> > On Fri, Jul 3, 2009 at 2:53 AM, Jarek Gawor <jgawor@gmail.com> wrote:
>> >>
>> >> Shawn,
>> >>
>> >> The one failure in console/advanced on Tomcat is caused by fixing tha=
t
>> >> prompting issue in the console. I'm hoping it's just a timing issue
>> >
>> > It's not a timing issue.=A0 This is caused by a modification on
>> > ConfirmMessageTag.java recently .
>> >
>> > After that=A0 change,=A0 dojo.js can't be found so that the prompting =
dialog
>> > can't be display anymore.
>> >
>> > Revert the bvt change and update the code
>> >
>> > private static final String DOJO_BASE =3D "/dojo/dojo"
>> >
>> > to
>> >
>> > private static final String DOJO_BASE =3D "/dojo"
>> >
>> > can fix this.
>> >>
>> >> since its takes a bit of time to load all the Dojo stuff for the firs=
t
>> >> time. So I just increased the wait time for the window to show up in
>> >> that test.
>> >>
>> >> Jarek
>> >>
>> >> On Wed, Jul 1, 2009 at 9:31 PM, Shawn Jiang<genspring@gmail.com> wrot=
e:
>> >> > I can't recreate the same console/advanced failure in my local
>> >> > machine.
>> >> > But I do find another console testsuite bug and filed a JIRA:
>> >> > https://issues.apache.org/jira/browse/GERONIMO-4720 =A0 (patch
>> >> > provided)
>> >> > The failure of enterprise-testsuite/sec-tests is related to
>> >> > "run-as"=A0propagation from a servlet to another servlet. =A0 I'm l=
ooking
>> >> > into
>> >> > it and will provide a patch.
>> >> > On Thu, Jun 25, 2009 at 11:58 PM, Jarek Gawor <jgawor@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> Based on running the testsuite yesterday and with fixes committed
>> >> >> last
>> >> >> night I *think* we should be passing all tests on Tomcat and fail
>> >> >> enterprise-testsuite/sec-tests and webservices-testsuite/jaxws-tes=
ts
>> >> >> on Jetty. The webservices-testsuite/jaxws-tests fails because of
>> >> >> GERONIMO-4645. Not sure what's going on with
>> >> >> enterprise-testsuite/sec-tests.
>> >> >>
>> >> >> Jarek
>> >> >>
>> >> >> On Thu, Jun 25, 2009 at 11:00 AM, Kevan
>> >> >> Miller<kevan.miller@gmail.com>
>> >> >> wrote:
>> >> >> > A search of emails shows that our last successful automated buil=
d
>> >> >> > of
>> >> >> > trunk
>> >> >> > was on May 26th. I know that there have been increasing
>> >> >> > frustration
>> >> >> > with
>> >> >> > these recent build issues. We seem to be closing in on getting
>> >> >> > these
>> >> >> > issues
>> >> >> > resolved. I built last night. I built successfully, last night,
>> >> >> > but
>> >> >> > had
>> >> >> > 7
>> >> >> > testsuite failures -- 3 jetty, 4 tomcat.
>> >> >> >
>> >> >> > I think it would do us a lot of good to have a concerted effort =
to
>> >> >> > get
>> >> >> > these
>> >> >> > final issues resolved. Here are the test failures that I'm seein=
g:
>> >> >> >
>> >> >> > 3 common errors:
>> >> >> >
>> >> >> > [INFO] The following tests failed:
>> >> >> > [INFO] =A0 =A0 * console-testsuite/advanced -
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > /Users/kevan/geronimo/server/trunk/testsuite/console-testsuite/a=
dvanced/build.log
>> >> >> > [INFO] =A0 =A0 * enterprise-testsuite/sec-tests -
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > /Users/kevan/geronimo/server/trunk/testsuite/enterprise-testsuit=
e/sec-tests/build.log
>> >> >> > [INFO] =A0 =A0 * webservices-testsuite/jaxws-tests -
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > /Users/kevan/geronimo/server/trunk/testsuite/webservices-testsui=
te/jaxws-tests/build.log
>> >> >> >
>> >> >> > 1 Tomcat unique failure:
>> >> >> >
>> >> >> > [INFO] =A0 =A0 * web-testsuite/test-tomcat -
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > /Users/kevan/geronimo/server/trunk/testsuite/web-testsuite/test-=
tomcat/build.log
>> >> >> >
>> >> >> > Is this consistent with what others are seeing?
>> >> >> >
>> >> >> > --kevan
>> >> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Shawn
>> >> >
>> >
>> >
>> >
>> > --
>> > Shawn
>> >
>
>
>
> --
> Shawn
>