Looks like maybe Thiago's 26d6212 and commits on Oct 29 & 31, I guess
an accident? App1TestCase.java &  BeanEditorTests.java

+ @TapestryTestConfiguration(webAppFolder = "src/test/app1",
browserStartCommand = "*googlechrome")



On Sun, Nov 3, 2013 at 6:09 AM, Ulrich Stärk <[email protected]> wrote:
> Since when are we running the tests with chrome? They used to be run with 
> firefox which is currently
> the only browser available on the build machine.
>
> Uli
>
> On 2013-11-02 18:25, Howard Lewis Ship wrote:
>> there may be other issues as well, I ran the full test suite succesfully
>> before rebasing thiago's changes, now there are failures. I'll be able to
>> look into it on monday.
>>
>> On Saturday, November 2, 2013, Bob Harner wrote:
>>
>>> According to [1] the current problem (or one of the problems) is that
>>> Selenium appears to be trying to start a Chrome browser and can't find
>>> one:
>>>
>>> ----------
>>> Message: Could not start Selenium session: Failed to start new browser
>>> session: java.lang.RuntimeException: java.lang.RuntimeException:
>>> Google Chrome could not be found in the path!
>>> Please add the directory containing ''chrome.exe' or 'google-chrome'
>>> or 'Google Chrome'' to your PATH environment
>>> variable, or explicitly specify a path to Google Chrome like this:
>>> *googlechrome /blah/blah/chrome.exe
>>> ----------
>>>
>>> [1]
>>> https://builds.apache.org/job/tapestry-trunk-freestyle/1175/testngreports/org.apache.tapestry5.beanvalidator.integration/org.apache.tapestry5.beanvalidator.integration.TapestryBeanValidationIntegrationTests/testStartup/
>>>
>>>
>>> On Fri, Nov 1, 2013 at 7:15 AM, Thiago H de Paula Figueiredo
>>> <[email protected] <javascript:;>> wrote:
>>>>
>>>> On Fri, 01 Nov 2013 08:14:31 -0200, Ulrich Stärk 
>>>> <[email protected]<javascript:;>>
>>> wrote:
>>>>
>>>>> As the log output says, tests run on port 4444. Also these are the only
>>> open ports atm:
>>>>
>>>>
>>>> Port 4444 is used by Selenium itself AFAIK. The Tapestry test webapps
>>> bind to 9090.
>>>>
>>>>
>>>>>
>>>>> root@tapbuild:~# lsof -i tcp|grep LISTEN
>>>>> sshd      698    root    3u  IPv4    3425      0t0  TCP *:ssh (LISTEN)
>>>>> sshd      698    root    4u  IPv6    3427      0t0  TCP *:ssh (LISTEN)
>>>>> java    17807 jenkins   15u  IPv6 2792628      0t0  TCP *:3141 (LISTEN)
>>>>>
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Uli
>>>>>
>>>>> On 2013-10-31 23:01, Andreas Ernst wrote:
>>>>>>
>>>>>> Am 31.10.13 22:59, schrieb Ulrich Stärk:
>>>>>>>
>>>>>>> I just checked on the machine that is running the Tapestry builds but
>>> there was nothing running
>>>>>>> except for a seemingly stale Jenkins client process. I killed it but
>>> I doubt that it was causing
>>>>>>> this problem. Port 4444 is not in use. Could it be that another test
>>> instance is started before the
>>>>>>> old one completely finished?
>>>>>>>
>>>>>>> Uli
>>>>>>>
>>>>>>> On 2013-10-31 22:16, Thiago H de Paula Figueiredo wrote:
>>>>>>>>
>>>>>>>> On Thu, 31 Oct 2013 17:35:55 -0200, Apache Jenkins Server
>>>>>>>> <[email protected] <javascript:;>> wrote:
>>>>>>>>
>>>>>>>>> See <
>>> https://builds.apache.org/job/tapestry-trunk-freestyle/1172/changes>
>>>>>>>>>
>>>>>>>>> MultiException[java.net.BindException: Address already in use,
>>> java.net.BindException: Address
>>>>>>>>> already in use]
>>>>>>>>
>>>>>>>>
>>>>>>>> Guys, any hints on how can I solve this? It seems there's some
>>> hanging old
>>>>>>>> Jetty instance.
>>>>>>
>>>>>>
>>>>>> What about port 8080?
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [email protected]<javascript:;>
>>>>> For additional commands, e-mail: 
>>>>> [email protected]<javascript:;>
>>>>>
>>>>
>>>>
>>>> --
>>>> Thiago H. de Paula Figueiredo
>>>> Tapestry, Java and Hibernate consultant and developer
>>>> http://machina.com.br
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [email protected]<javascript:;>
>>>> For additional commands, e-mail: [email protected]<javascript:;>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected] <javascript:;>
>>> For additional commands, e-mail: [email protected]<javascript:;>
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to