Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Auto Closed
-
None
-
None
-
None
Description
https://travis-ci.org/github/apache/fineract/builds/739089394 for https://github.com/apache/fineract/pull/1465 failed with:
> Task :integration-tests:test ClientLoanIntegrationTest > checkClientLoanCreateAndDisburseFlow() FAILED java.lang.AssertionError: 1 expectation failed. Expected status code <200> but was <403>. (...) at org.apache.fineract.integrationtests.common.Utils.performServerPost(Utils.java:159) at org.apache.fineract.integrationtests.common.loans.LoanTransactionHelper.getLoanProductId(LoanTransactionHelper.java:78) at org.apache.fineract.integrationtests.ClientLoanIntegrationTest.createLoanProduct(ClientLoanIntegrationTest.java:905) at org.apache.fineract.integrationtests.ClientLoanIntegrationTest.checkClientLoanCreateAndDisburseFlow(ClientLoanIntegrationTest.java:109) ClientLoanIntegrationTest > testLoanScheduleWithInterestRecalculation_WITH_ORIGINAL_REPAYMENT_BASED_ARREARS_AGEING() SKIPPED
This reminds me of FINERACT-885.. do we perhaps still (again) have a new date issue that breaks the integration test on the last couple of days every month?
Or could this somehow be related to an impact of https://github.com/apache/fineract/pull/1179 for FINERACT-826? Just a.. hunch.
NB Expected status code <200> but was <403>, where HTTP 403 = https://en.wikipedia.org/wiki/HTTP_403 would be a Permission / Authorization issue, not a failed data validation (if it's accurate; but it's well possible Fineract sends inappropriate HTTP response codes, of course).
ptuomola any other thoughts?