Mailing-List: contact dev-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: pass (nike.apache.org: domain of brent.atkinson@gmail.com
 designates 209.85.212.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <788B73D4-8333-497D-8D1B-C48C93DFF168@apache.org>
References: <E4C6276D-845F-4373-ABF9-59175C0601BB@apache.org>
	<CALyHw0Gs6xAt2Qyt8608jTA=QO7B+30jJqs6ZrCvc__Eyxvkxg@mail.gmail.com>
	<386A8714-F7CA-4E36-8DBB-A5AB9533A55A@apache.org>
	<CALyHw0E_2hF2Xnm95-jNK5zKifsMCMdrUeHSEuu+9+ZK2dTjXw@mail.gmail.com>
	<B1D409CA-F8BA-4AC6-94EC-EA4AD11F77BE@apache.org>
	<CALyHw0GbyK=WhRpH25LatF3UTOAQHDApS6Do2pMnb+rVEK_PwA@mail.gmail.com>
	<6910AB36-097F-4EDC-8D7E-4464D6792C24@apache.org>
	<CALyHw0GtKFap8dJZpG7k_1zEMuLQZoe_pWkGp4zT7YN6K+V4Mw@mail.gmail.com>
	<B715EBF4-39D4-4B4D-8FF1-56E24A3D4563@apache.org>
	<A9E04939-2954-4B2C-8059-F557AF2947B1@apache.org>
	<CALyHw0GF9sKPXaXf6Gm5sQNq7BAx2D3RK-Tp3qT4rUHac1Va2A@mail.gmail.com>
	<CALyHw0H4jW97b7YmmNvPuorrFeLz7nkjiKKH=Fhy_JQUvCm6bw@mail.gmail.com>
	<252B56BF-6E78-4E14-81CC-C614F45341C1@apache.org>
	<CALyHw0ECNYzTQPdVgUxBM1gayFSmquTaW0Dji+JDj1P_HM3v8g@mail.gmail.com>
	<CALyHw0FpRaUd1U=emWNp5W8syWaD7GfESNHB06q2wDG7s+o6jQ@mail.gmail.com>
	<4C714B20-DA53-4CC4-A5A6-6DBFB54FBA9E@apache.org>
	<CALyHw0Ejfk6xT6RY=+E_90cBzTetLLQZFCpY0uWkTqOXNcm+5A@mail.gmail.com>
	<788B73D4-8333-497D-8D1B-C48C93DFF168@apache.org>
Date: Tue, 21 Aug 2012 14:09:01 -0400
Message-ID: 
 <CALyHw0Hb_yw1jCj+cVD7Kf4JMA=J99wOhjO6YtMRbiCUFuJJHA@mail.gmail.com>
Subject: Re: Getting Selenium tests updated
From: Brent Atkinson <brent.atkinson@gmail.com>
To: dev@continuum.apache.org
Content-Type: multipart/alternative; boundary=f46d043bdb4e6262e704c7ca859d

--f46d043bdb4e6262e704c7ca859d
Content-Type: text/plain; charset=ISO-8859-1

Yes, I will try to:

* cover windows with a similar test if feasible: build.bat
* fix the path validation
* discover the source of the deletion issue... I think it is a file handle
as you said... will check and try to track it down if your fix doesn't
address it for me.

Brent
On Aug 21, 2012 9:57 AM, "Brett Porter" <brett@apache.org> wrote:

>
> On 21/08/2012, at 2:08 PM, Brent Atkinson <brent.atkinson@gmail.com>
> wrote:
>
> > The time outs might be due to the fact that the build still appears to be
> > trying to execute build.sh (DistributedBuildTest.java:156).
>
> So, these just need to be disabled on Windows - or we could have a
> build.bat alternative for that?
>
> >
> > The testAddMavenToolWithBuildEnvironment failure appears to be because of
> > the characters in my Windows path "C:\Program Files (x86)\Apache Software
> > Foundation\apache-maven-2.2.1\bin\.."
>
> Looks like overly strict validation - would you be comfortable fixing that
> up?
>
> >
> > I can't see why the ReleaseTest.java's setUp() fails, but I think it
> might
> > be running up against a path length limitation.
>
> Shouldn't be... it's only in target/conf/prepared-releases of your test
> checkout. I think there's a chance that it's an open file handle - I just
> fixed an unlikely one, did that help?
>
> - Brett
>
>

--f46d043bdb4e6262e704c7ca859d--