On 6/25/07, Vladimir Ivanov <[EMAIL PROTECTED]> wrote:
On 6/22/07, Tim Ellison <[EMAIL PROTECTED]> wrote:
> Vladimir Ivanov wrote:
> > On 6/22/07, Tim Ellison <[EMAIL PROTECTED]> wrote:
> >> Is it possible that a firewall is blocking access to that server?
I exclude this test locally on both linuxes. When I tune environment I
will add this test to run cycles again.
So, classlib tests on Linux x86 should report 'passed' status soon and
continue to fail on Linux x86_64 due to AWT test failure.
thanks, Vladimir
> >
> > Yes. The 'outside' world is accessible through the proxy only. So if
> > test tries to use 'direct connect to internet' it will fail.
>
> So you should either tweak the jre/lib/net.properties for the particular
> configuration you require, or pass in some ${hy.test.vmargs} to define
> the proxy.
With updated file net.properties (by http proxy settings) this test
reports 'passed' status but 7 tests from the
tests.api.java.net.ProxySelectorTest class failed:
test_selectLjava_net_URI_SelectExact_NullHost
test_selectLjava_net_URI_SelectExact_
test_selectLjava_net_URI_SelectExact_InvalidPort
test_selectLjava_net_URI_SelectLikeHTTP
test_selectLjava_net_URI_SelectNoHTTP
test_connectionFailedLjava_net_URILjava_net_SocketAddressLjava_io_IOException
test_selectLjava_net_URI_SelectExact
So, it is not a good solution to update this file.
thanks, Vladimir
>
> I realize that requiring a connection to the internet to run tests is
> not ideal, and that we have that requirement in a number of places.
>
> Regards,
> Tim
>
