[jira] [Commented] (FINERACT-1016) Flaky RecurringDepositTest.testPrematureClosureAmountWithPenalInterestTillPrematureWithdrawal_With_360_Days()

["Michael Vorburger (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FINERACT-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123360#comment-17123360 ] 

Michael Vorburger commented on FINERACT-1016:
---------------------------------------------

https://github.com/apache/fineract/pull/968 proposes to (temparily) {{@Ignore}} this test, as per https://github.com/apache/fineract#pull-requests.

It would, of course, be great if we could actually really fix it.

> Flaky RecurringDepositTest.testPrematureClosureAmountWithPenalInterestTillPrematureWithdrawal_With_360_Days()
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: FINERACT-1016
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1016
>             Project: Apache Fineract
>          Issue Type: Sub-task
>            Reporter: Michael Vorburger
>            Priority: Major
>
> See comments in FINERACT-855 from yesterday and today re. testPrematureClosureAmountWithPenalInterestTillPrematureWithdrawal_With_360_Days():
> That problem actually probably actually has nothing at all to do with the testRecurringDepositAccountWithClosureTypeTransferToSavings_WITH_HOLD_TAX() failure which FINERACT-855 was originally about, so let's track this separately here.
> The testPrematureClosureAmountWithPenalInterestTillPrematureWithdrawal_With_360_Days() failure today seems to have nothing to do with the Job Scheduler (for once), but appears to be some date related mess.
> That test today right for me reliably fails locally, but when I change my system date back a few days to late May, then it passes. So either the test, or worse even the actual logic being tested, has some bug in date handling.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)