[
https://issues.apache.org/jira/browse/JCR-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved JCR-1764.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.5
Hmm, that's because the nodes are dequeued before they are actually added to
the index.
I've added additional synchronization to the test case, which should fix the
issue. Please re-open if you still see test failures.
Fixed in revision: 698946
> Occasional IndexingQueueTest failures
> -------------------------------------
>
> Key: JCR-1764
> URL: https://issues.apache.org/jira/browse/JCR-1764
> Project: Jackrabbit
> Issue Type: Bug
> Components: indexing, jackrabbit-core
> Reporter: Jukka Zitting
> Priority: Minor
> Fix For: 1.5
>
>
> Every now and then, when doing a clean build of the latest jackrabbit trunk I
> see the following test failure in jackrabbit-core:
> -------------------------------------------------------------------------------
> Test set: org.apache.jackrabbit.core.query.lucene.TestAll
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.665 sec <<<
> FAILURE!
> testQueue(org.apache.jackrabbit.core.query.lucene.IndexingQueueTest) Time
> elapsed: 1.654 sec <<< FAILURE!
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.assertTrue(Assert.java:20)
> at junit.framework.Assert.assertTrue(Assert.java:27)
> at
> org.apache.jackrabbit.core.query.lucene.IndexingQueueTest.testQueue(IndexingQueueTest.java:69)
> Typically the problem disappears when I rebuild, but the test should still
> not have failed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
