[
https://issues.apache.org/jira/browse/FINERACT-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17098277#comment-17098277
]
Petri Tuomola commented on FINERACT-855:
----------------------------------------
As far as I could work out, this is a timing issue re scheduling the job:
Quartz does not have time to process the job submission before we request the
status of the job, and hence when we request the job status, it's neither
completed nor currentlyRunning as expected by the code.
I fixed this in FINERACT-730 by adding a short delay between job submission and
first status check. A more clever fix could be to enhance the job status check
to also cater for a scenario where the job has not yet been started...
> RecurringDepositTest
> --------------------
>
> Key: FINERACT-855
> URL: https://issues.apache.org/jira/browse/FINERACT-855
> Project: Apache Fineract
> Issue Type: Sub-task
> Reporter: Michael Vorburger
> Priority: Major
>
> while attempting to understand FINERACT-852, and locally pulling and running
> https://github.com/apache/fineract/pull/719, it failed for me, and we have a
> note about a similar failure in https://github.com/apache/fineract/pull/642,
> this may be another flaky one?
> {code}> Task :integrationTest
>
>
>
>
>
> org.apache.fineract.integrationtests.RecurringDepositTest >
> testRecurringDepositAccountWithClosureTypeTransferToSavings_WITH_HOLD_TAX
> FAILED
> java.lang.AssertionError at RecurringDepositTest.java:836{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
