DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31589>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31589 Problems specific to OpenVMS ------- Additional Comments From [EMAIL PROTECTED] 2004-10-07 21:32 ------- A lot of these seem to have an underlying cause; file system differences. For example, lots of tests fail as an expected file isn't where we expect it. We also seem to get different return codes from forked java programs, which may be related to either the way VMS does returns differently, <touch> doesnt set dates: [junit] Testcase: testMillis(org.apache.tools.ant.taskdefs.TouchTest): FAILED [junit] Time 662256000000 is not within 1000 ms of 3813679200000 [junit] junit.framework.AssertionFailedError: Time 662256000000 is not within 1000 ms of 3813679200000 [junit] at junit.framework.Assert.fail(Assert.java) [junit] at junit.framework.Assert.assertTrue(Assert.java) [junit] at org.apache.tools.ant.taskdefs.TouchTest.assertTimesNearlyMatch(TouchTest.java) This looks like File.touch() doesn't work, as whenever Ant tries to put the clock back on a file, we get a failure. Is this a known feature of the VMS JVM? The other file system test that fails everywhere is File.isDirectory(). A lot of tests verify that directories are not valid sources, and this isnt being picked up. Again, is this a known VMS quirk? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
