You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Petri Tuomola (Jira)" <ji...@apache.org> on 2020/06/04 09:34:00 UTC
[jira] [Commented] (FINERACT-899) Flaky
AccountingScenarioIntegrationTest
checkPeriodicAccrualAccountingFlow_OVER_PAYMENT
[ https://issues.apache.org/jira/browse/FINERACT-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125744#comment-17125744 ]
Petri Tuomola commented on FINERACT-899:
----------------------------------------
[~vorburger] I've been trying to reproduce this locally but have not been able to, so probably something linked to dates again. Not sure how we best get a way to reproduce this... maybe we could re-enable this so we see when it starts failing?
> Flaky AccountingScenarioIntegrationTest checkPeriodicAccrualAccountingFlow_OVER_PAYMENT
> ---------------------------------------------------------------------------------------
>
> Key: FINERACT-899
> URL: https://issues.apache.org/jira/browse/FINERACT-899
> Project: Apache Fineract
> Issue Type: Bug
> Reporter: Michael Vorburger
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> https://travis-ci.org/github/apache/fineract/builds/676392200 for https://github.com/apache/fineract/pull/767 just failed due to:
> {noformat}> Task :integrationTest
> org.apache.fineract.integrationtests.AccountingScenarioIntegrationTest > checkPeriodicAccrualAccountingFlow_OVER_PAYMENT FAILED
> java.lang.AssertionError at AccountingScenarioIntegrationTest.java:703{noformat}
> That PR is a simply clean up, so this looks like it's another "spurios" test failure.
> If it happens more often, we could {{@Ignore}} (like FINERACT-852).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)