[
https://issues.apache.org/jira/browse/UNOMI-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16521573#comment-16521573
]
Serge Huber commented on UNOMI-184:
-----------------------------------
I have just committed a fix for these integration test failures. Problem was
due to the reloading of property types while ElasticSearch was still indexing,
making the newly created property not yet available. Fixed by changing the
reload frequency from 5 seconds to 10 seconds. We really need to make these
timers configurable though, but this will be done at a later point in time.
Also included in this fix :
- The integration tests will now setup the camel context in "tracing" mode,
making issues easier to debug. This is only done during integration tests, by
default tracing is disabled.
- Improved error logging in LineSplitProcessor, this will also make catching
other problems with this processor hopefully easier.
> Integration tests will fail "randomly"
> --------------------------------------
>
> Key: UNOMI-184
> URL: https://issues.apache.org/jira/browse/UNOMI-184
> Project: Apache Unomi
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.3.0-incubating
> Reporter: Serge Huber
> Priority: Blocker
> Fix For: 1.3.0-incubating
>
>
> On some platforms, integration tests will fail "randomly", mostly in the
> profile import/export tests.
> We need to fix this before we can release the new 1.3.0 release.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
