On 12/2/2010 7:50 PM, Pavel Tisnovsky wrote:
Looks like this is a problem with your patched IcedTea jtreg harness rather than with the test itself then.The same behaviour could be also reported on unpatched JTreg Harness 4.0. (so it's just another reason to update JTreg harness to 4.1 on IcedTea6 ;)
So are you saying that jtreg 4.1 works correctly, and this issue is specific to version 4.0 only?
-- best regards, Anthony
