You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Dominique Devienne <DD...@lgc.com> on 2002/07/06 17:29:45 UTC
Problem with latest Selector patch?
Fresh sandbox of Ant branch 1.5 from this morning. Just did bootstrap and
build test. Win2K, JDK 1.4.0_01. --DD
Testcase:
testSelectionBehaviour(org.apache.tools.ant.types.selectors.DateSelectorTest
): FAILED
expected:<TTFFTFFFTTTT> but was:<TFFFFFFFFFFT>
junit.framework.AssertionFailedError: expected:<TTFFTFFFTTTT> but
was:<TFFFFFFFFFFT>
at junit.framework.Assert.fail(Assert.java:51)
at junit.framework.Assert.failNotEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:68)
at junit.framework.Assert.assertEquals(Assert.java:75)
at
org.apache.tools.ant.types.selectors.DateSelectorTest.testSelectionBehaviour
(DateSelectorTest.java:232)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at junit.framework.TestCase.runTest(TestCase.java:166)
at junit.framework.TestCase.runBare(TestCase.java:140)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:131)
at junit.framework.TestSuite.runTest(TestSuite.java:173)
at junit.framework.TestSuite.run(TestSuite.java:168)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRu
nner.java:325)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnitTask
.java:804)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.jav
a:551)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.jav
a:527)
at org.apache.tools.ant.Task.perform(Task.java:317)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:334)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
at org.apache.tools.ant.Main.runBuild(Main.java:610)
at org.apache.tools.ant.Main.start(Main.java:196)
at org.apache.tools.ant.Main.main(Main.java:235)
BUILD FAILED
file:D:/org_apache/jakarta-ant15/build.xml:1227: Test
org.apache.tools.ant.types.selectors.DateSelectorTest failed
Total time: 5 minutes 20 seconds
D:\org_apache\jakarta-ant15>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Problem with latest Selector patch?
Posted by Bruce Atherton <br...@callenish.com>.
At 09:19 AM 7/8/2002 +0200, Stefan Bodewig wrote:
>java full version "Linux_JDK_1.1.8_v3_green_threads"
>
> [junit] Testcase:
> testSelectionBehaviour(org.apache.tools.ant.types.selectors.PresentSelectorTest):
> FAILED
> [junit] expected:<TTTTTFFFFFFF> but was:<TTTTTTTTTTTF>
> [junit] junit.framework.AssertionFailedError: expected:<TTTTTFFFFFFF>
> but was:<TTTTTTTTTTTF>
The behaviour you are seeing is what is expected with a post-1.1 JDK.
Evidently your Linux JDK 1.1 works properly where the Windows 1.1 JDK (at
least) does not. I assume yours is blackdown? Perhaps that variation needs
to be run only on a windows 1.1 VM. I'll try installing blackdown and see.
>java full version "JDK-1.2.2_012"
>java full version "1.3.1_03-b03"
>java full version "1.4.0-b92"
>
>all fail with
>
> [junit] Testcase:
> testSelectionBehaviour(org.apache.tools.ant.types.selectors.DateSelectorTest):
> FAILED
> [junit] expected:<TTFFTFFFTTTT> but was:<TFFFFFFFFFFT>
> [junit] junit.framework.AssertionFailedError: expected:<TTFFTFFFTTTT>
> but was:<TFFFFFFFFFFT>
>
>at line 232.
This is frustrating because I can't duplicate it. I have a suspicion what
is causing the problem, though, and if I am right at least it doesn't
indicate a bug in DateSelector.
Both problematic lines come from selecting on a specific millisecond time,
1006347300000L. On my boxen, this is identical to "11/21/2001 4:55 AM" but
I'm guessing that isn't the case on yours and Dominique's. Particularly
because a previous test reads in that same time from the timestamp on a
file and does the selection that way, and that test isn't failing for you.
I'm commenting these tests out for now. I'd hate to hold up 1.5 on account
of them, and I really think they are an artifact of the testing rather than
a bug.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Problem with latest Selector patch?
Posted by Stefan Bodewig <bo...@apache.org>.
OK, tests on my Redhat 7.2 box:
java full version "Linux_JDK_1.1.8_v3_green_threads"
[junit] Testcase: testSelectionBehaviour(org.apache.tools.ant.types.selectors.PresentSelectorTest): FAILED
[junit] expected:<TTTTTFFFFFFF> but was:<TTTTTTTTTTTF>
[junit] junit.framework.AssertionFailedError: expected:<TTTTTFFFFFFF> but was:<TTTTTTTTTTTF>
java full version "JDK-1.2.2_012"
java full version "1.3.1_03-b03"
java full version "1.4.0-b92"
all fail with
[junit] Testcase: testSelectionBehaviour(org.apache.tools.ant.types.selectors.DateSelectorTest): FAILED
[junit] expected:<TTFFTFFFTTTT> but was:<TFFFFFFFFFFT>
[junit] junit.framework.AssertionFailedError: expected:<TTFFTFFFTTTT> but was:<TFFFFFFFFFFT>
at line 232.
I'll look into it later today.
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>