[
https://issues.apache.org/jira/browse/FINERACT-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17092639#comment-17092639
]
Michael Vorburger commented on FINERACT-899:
--------------------------------------------
https://travis-ci.org/github/apache/fineract/builds/679659779 for
https://github.com/apache/fineract/pull/782 failed in
AccountingScenarioIntegrationTest > checkPeriodicAccrualAccountingFlow so
https://github.com/apache/fineract/pull/785 proposed to ignore that one as
well, based on https://github.com/apache/fineract/pull/782.
If we get more than 2 test methods failing in a test class, then should we
just ignore the entire test class instead?
> 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)
