[jboss-jira] [JBoss JIRA] (DROOLS-1696) Events that are already expired at insert time, doesn't always produce activations
[
https://issues.jboss.org/browse/DROOLS-1696?page=com.atlassian.jira.plugi...
]
Tibor Zimányi commented on DROOLS-1696:
---------------------------------------
Rewrote the test using pseudoclock. Now it looks like some @timestamp problem, because
when advancing time between insertions [1], the test fails, but if the events are inserted
at the same time, it works. Note that insertion time shouldn't influence fires,
because inserted events have their own timestamp defined.
[1]
https://github.com/kiegroup/drools/pull/1410/files#diff-1b0fe819447feb373...
Events that are already expired at insert time, doesn't always
produce activations
----------------------------------------------------------------------------------
Key: DROOLS-1696
URL: https://issues.jboss.org/browse/DROOLS-1696
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.1.0.Final
Reporter: Tibor Zimányi
Assignee: Mario Fusco
Fix For: 7.2.0.Final
When inserting events that have timestamp in the past and don't have expiration
defined (@expires), the events don't always produce activations. See a test example
[1]. This test fails "randomly".
I will create a PR with a reproducer.
[1] https://gist.github.com/baldimir/fb9808ce1e6d49c83dc24570b3cb6093
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)