-
1. Re: Recent changes to VFS jar processing
bill.burke Nov 30, 2006 9:12 AM (in response to adrian.brock)Which tests are failing? VFS tests? I did make some changes to JarHandler so that it returned non-"jar:" based URLs. I reran the VFS testsuite and everything passed except a test that had failed before.
-
2. Re: Recent changes to VFS jar processing
adrian.brock Nov 30, 2006 9:29 AM (in response to adrian.brock)It's ok, I found the problem.
The issue was that the serailization was truncating the url incorrectly.file:/tmp/.... -> tmp/...
missing the leading /
There are no failing vfs tests? -
3. Re: Recent changes to VFS jar processing
bill.burke Nov 30, 2006 9:32 AM (in response to adrian.brock)Only one failing VFS test (in container module).
-
4. Re: Recent changes to VFS jar processing
adrian.brock Nov 30, 2006 9:46 AM (in response to adrian.brock)Which one? When I run the VFSAllTestSuite I get:
... Time: 1.374 OK (313 tests)
-
5. Re: Recent changes to VFS jar processing
bill.burke Nov 30, 2006 9:57 AM (in response to adrian.brock)don't remember. It was one of the tests that test number of bytes read from stream, or something like that...
I can't run the testsuite now as I've been doing some VFS work in the code on my laptop -
6. Re: Recent changes to VFS jar processing
starksm64 Nov 30, 2006 11:13 AM (in response to adrian.brock)I fixed the failing test. It was inconsistent resolution of a file timestamp vs a jar entry timestamp on win32. The win32 timestamp was not using millisecond resolution so I dropped that portion of the check.