It turns out the recent failures on Solaris x64 hudson are due to an
illegal character in the URI host name string:
Testcase:
testCrossPlatformNormalise(org.apache.river.impl.net.UriStringTest):
Caused an ERROR
Illegal character in hostname at index 13:
http://hudson_solaris:9081/nonactiva
bject: PreferredClassProvider: URL and URI
It turns out the recent failures on Solaris x64 hudson are due to an
illegal character in the URI host name string:
Testcase:
testCrossPlatformNormalise(org.apache.river.impl.net.UriStringTest):
Caused an ERROR
Illegal character in hostname at index 13:
r.apache.org
Subject: PreferredClassProvider: URL and URI
It turns out the recent failures on Solaris x64 hudson are due to an
illegal character in the URI host name string:
Testcase:
testCrossPlatformNormalise(org.apache.river.impl.net.UriStringTest):
Caused an ERROR
Illegal character in hostna
gt; From: Peter Firmstone [mailto:j...@zeus.net.au]
>> Sent: Monday, August 06, 2012 7:39 AM
>> To:dev@river.apache.org
>> Subject: PreferredClassProvider: URL and URI
>>
>> It turns out the recent failures on Solaris x64 hudson are due to an
>> illegal character in the URI host na
To:dev@river.apache.org
Subject: PreferredClassProvider: URL and URI
It turns out the recent failures on Solaris x64 hudson are due to an
illegal character in the URI host name string:
Testcase:
testCrossPlatformNormalise(**org.apache.river.impl.net.**UriStringTest):
Caused an ERROR
Illegal characte