Hello All,
PR: https://github.com/apache/fineract/pull/764 by Mike has been merged.
This is a temporal fix which deactivates the failing scheduler job tests
until someone can fix it properly. This is just to keep development going
for the project.
IS there anyone out there, reading this who wants
Hi Michael,
... should have been more precise with the testcontainer approach... in
terms of actual code changes: it's not a lot (biggest change was that I
introduced a base class that contains the test rule to fire up the required
containers)... can't remember exactly how many fixes I added, but
Quick follow-up: The biggest issue (FINERACT-852) seems to be related to
that scheduler thing... I suspect this is something like the tests
sometimes (often) are not waiting long enough (perhaps when Travis CI is a
little more loaded?) for those background jobs to complete? Or the jobs
sometimes fa
Aleksandar,
Thanks for engaging.
FYI it's actually always the same few tests which fail frequently on us,
see sub-tasks and links from
https://issues.apache.org/jira/browse/FINERACT-850. Today specifically I've
myself hit (only) https://issues.apache.org/jira/browse/FINERACT-852 on x3
PRs. So rew
Hi,
... just saw this message... I had a stab at the integration tests a while
back and fixed quite a bit... but had a bit of a different approach... I've
added Testcontainers to the mix (that was the biggest change) and fixed
then all failing tests until I got - if I'm not mistaken - 93% success
Is there really nobody e.g. from any partners using Fineract who have an
interest in contributing someone's time to help stabilizing flaky
integration tests? This is quite a PITA, and any help on
https://issues.apache.org/jira/browse/FINERACT-850 related issues would be
much appreciated by the proj
> file a bug report on our Issue tracker on JIRA
FYI all, Yemdjih created https://issues.apache.org/jira/browse/FINERACT-850
to track this. (Yemdjih, when you create JIRA issues in response to mailing
list threads, it's best if you reply on the thread with a link, so people
interested can watch th
To me this is very interesting
java.lang.NoClassDefFoundError: org/w3c/dom/ls/DocumentLS
I am facing this issues
Do i need to install this as a dependency or i need to provide some
specific class path while building .
As i know this should be the part of the Jdk.
On Sat, Mar 7, 2020 at 3
org.apache.fineract.notification.SenderTest > notificationCreation FAILED
java.lang.IllegalStateException at
DefaultCacheAwareContextLoaderDelegate.java:132
Caused by:
org.springframework.beans.factory.BeanDefinitionStoreException at
XmlBeanDefinitionReader.java:420
Cause
Hi All,
I looked at these again and it seems the inconsistencies in tests might be
reduced or caught very early if before sending PRs, we run the following:
./gradlew clean build
./gradlew clean check
./gradlew clean integrationTest
So we make sure all is working on Dev env before sending PRs.
I see the logs reflect this case. Please..file a bug report on our Issue
tracker on JIRA ANd provide as much detail as possible. The slow
queries mayb indicate an underlying somewhere on the code base
Is anyone able to investigate this more and see if they can shed some light
on this?
Thanks.
Not sure why this is happening now but for some days now Integration Tests
have been acting funny even on branch develop.
Sometimes they work fine(1 / 5 trials) and others they fail. There is a
repetitive 6 test case failures and they are all related to DB queries.
Logs show slow queries and exis
Hey Carl, are the tests fine now?
On Wed, 5 Jun 2019 at 10:04, carl collins
wrote:
> I didn't. I will try that now
>
> On Wed, Jun 5, 2019 at 5:40 AM Santosh Math <
> sant...@confluxtechnologies.com> wrote:
>
>> Hi Carl,
>>
>> Did you run it in fresh database? or drop the database, recreate and
Hi Carl,
The fresh DB suggestion by Santosh was a good idea.
I had similar issues about failing integration tests on my local environment
only.
If you are making a PR to Fineract, then it automatically runs Travis CI with
correct testing configuration and you can be sure it's correct.
Ho
Hi Santosh,
I dropped the database,then recreated it as you suggested. This time when
I run the integration tests, 3 tests fail as seen in the screenshot of the
report attached.
Thanks
Carl
On Wed, Jun 5, 2019 at 8:04 AM carl collins
wrote:
> I didn't. I will try that now
>
> On Wed, Jun 5,
I didn't. I will try that now
On Wed, Jun 5, 2019 at 5:40 AM Santosh Math
wrote:
> Hi Carl,
>
> Did you run it in fresh database? or drop the database, recreate and then
> run it.
>
> On Mon, Jun 3, 2019 at 8:44 PM carl collins
> wrote:
>
>> Hello ,
>> I am Carl Collins Wayig, a software engin
Hi Carl,
Did you run it in fresh database? or drop the database, recreate and then
run it.
On Mon, Jun 3, 2019 at 8:44 PM carl collins
wrote:
> Hello ,
> I am Carl Collins Wayig, a software engineering student from Cameroon. I
> will love to contribute to the fineract project. I have setup fin
Hello ,
I am Carl Collins Wayig, a software engineering student from Cameroon. I
will love to contribute to the fineract project. I have setup fineract
locally and while running integration tests some tests failed. Attached to
this email is a picture of test summary generated.
18 matches
Mail list logo