camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem Jiang <willem.ji...@gmail.com>
Subject Re: [jira] Created: (CAMEL-1135) TestEndpointTest Unit test failed which may be caused by recent change of File Component
Date Mon, 01 Dec 2008 15:00:07 GMT
Hi Claus,

The test error came from a no-windows box :(

I did a quick test by adding the idemotent=true option, it doesn't work yet.

But if I change the consumer.delay=2000 to consumer.delay=4000, I can
just get 2 file message instead of 4 file message in my Vista box.

BTW, there is no any description of noop=true&idempotent=true *now* in
the File wiki.

Willem


Claus Ibsen wrote:
> Set idemotent=true as a URI option and it should stop getting the same
> file over and over again.
> 
> However it passed on my XP all the time.
> 
> Basically testing with noop=true *before*
> should be noop=true&idempotent=true *now*
> 
> /Claus Ibsen
> Apache Camel Committer
> Blog: http://davsclaus.blogspot.com/
> 
> 
> 
> On Mon, Dec 1, 2008 at 3:38 PM, Willem Jiang (JIRA) <jira@apache.org> wrote:
>> TestEndpointTest  Unit test failed which may be caused by recent change of File Component
>> -----------------------------------------------------------------------------------------
>>
>>                 Key: CAMEL-1135
>>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1135
>>             Project: Apache Camel
>>          Issue Type: Bug
>>          Components: camel-core
>>    Affects Versions: 2.0.0
>>            Reporter: Willem Jiang
>>             Fix For: 2.0.0
>>
>>
>> Here are the stack trace of the TestEndpointTest.testMocksAreValid on different machines
>>
>> org.apache.camel.component.test.TestEndpointTest.testMocksAreValid =================
>> java.lang.AssertionError: test:file://src/test/data?noop=true&consumer.recursive=true&consumer.delay=2000
Received message count. Expected: <567> but was: <78>
>>        at org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:712)
>>        at org.apache.camel.component.mock.MockEndpoint.assertEquals(MockEndpoint.java:694)
>>        at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:238)
>>        at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:214)
>>        at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:141)
>>        at org.apache.camel.component.test.TestEndpointTest.testMocksAreValid(TestEndpointTest.java:49)
>>
>> org.apache.camel.component.test.TestEndpointTest.testMocksAreValid =================
>> java.lang.AssertionError: test:file://src/test/data?noop=true&consumer.recursive=true&consumer.delay=2000
Received message count. Expected: <219> but was: <78>
>>        at org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:712)
>>        at org.apache.camel.component.mock.MockEndpoint.assertEquals(MockEndpoint.java:694)
>>        at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:238)
>>        at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:214)
>>        at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:141)
>>        at org.apache.camel.component.test.TestEndpointTest.testMocksAreValid(TestEndpointTest.java:49)
>>
>> I don't know why the test endpoint could get so many received message.
>>
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>>
> 


Mime
View raw message