> 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 the respective issue and comment on it.) I've also just create a new https://issues.apache.org/jira/browse/FINERACT-852 for another flaky IT.
It's a weird problem, seems to be concurrency related. Contributions fixing this would certainly be very very welcome! PS: Saransh, the problem you point out below is I think something entirely different? I've not seen that particular problem on any failed Travis build on any PR - have you? I suspect that you are only hitting this locally, and it is totally unrelated to the flaky integration tests on some PRs. If I had to guess, I would suspect something with your local JDK installation... e.g. you wouldn't happen to have hit the problem you show below this while playing with Java 11, and forgot to switch back to Java 8 which Fineract is currently on? ;-) On Sat, Mar 7, 2020 at 10:57 AM Saransh Sharma <sara...@muellners.com> wrote: > 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:18 PM Saransh Sharma <sara...@muellners.com> > wrote: > >> 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 >> >> Caused by: java.lang.NoClassDefFoundError at >> ClassLoader.java:-2 >> >> Caused by: java.lang.ClassNotFoundException at >> BuiltinClassLoader.java:581 >> >> >> org.apache.fineract.mix.report.service.XBRLBuilderTest > >> shouldCorrectlyBuildMap FAILED >> >> java.lang.NoClassDefFoundError at XBRLBuilderTest.java:79 >> >> Caused by: java.lang.ClassNotFoundException at >> XBRLBuilderTest.java:79 >> >> >> org.apache.fineract.commands.provider.CommandHandlerProviderTest > >> shouldThrowUnsupportedCommandException FAILED >> >> java.lang.IllegalStateException at >> DefaultCacheAwareContextLoaderDelegate.java:132 >> >> Caused by: >> org.springframework.beans.factory.BeanDefinitionStoreException at >> XmlBeanDefinitionReader.java:420 >> >> Caused by: java.lang.NoClassDefFoundError at >> ClassLoader.java:-2 >> >> Caused by: java.lang.ClassNotFoundException at >> BuiltinClassLoader.java:581 >> >> >> org.apache.fineract.commands.provider.CommandHandlerProviderTest > >> shouldRegisterHandler FAILED >> >> java.lang.IllegalStateException at >> DefaultCacheAwareContextLoaderDelegate.java:132 >> >> Caused by: >> org.springframework.beans.factory.BeanDefinitionStoreException at >> XmlBeanDefinitionReader.java:420 >> >> Caused by: java.lang.NoClassDefFoundError at >> ClassLoader.java:-2 >> >> Caused by: java.lang.ClassNotFoundException at >> BuiltinClassLoader.java:581 >> >> >> org.apache.fineract.infrastructure.configuration.spring.SpringConfigurationTest >> > testSpringXMLConfiguration FAILED >> >> java.lang.IllegalStateException at >> DefaultCacheAwareContextLoaderDelegate.java:132 >> >> Caused by: >> org.springframework.beans.factory.BeanDefinitionStoreException at >> XmlBeanDefinitionReader.java:420 >> >> Caused by: java.lang.NoClassDefFoundError at >> ClassLoader.java:-2 >> >> Caused by: java.lang.ClassNotFoundException at >> BuiltinClassLoader.java:581 >> >> >> On Sat, Mar 7, 2020 at 3:16 PM Saransh Sharma <sara...@muellners.com> >> wrote: >> >>> Talking about tests >>> >>> I just ran ./gradlew clean build >>> >>> It fails with these errors. Though i did not do any changes in the >>> mentioned packages. >>> >>> Is it normal> >>> >>> On Fri, Mar 6, 2020 at 12:35 AM Awasum Yannick <awa...@apache.org> >>> wrote: >>> >>>> 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 hope this helps >>>> >>>> On Wed, Mar 4, 2020 at 10:34 PM Awasum Yannick <awa...@apache.org> >>>> wrote: >>>> >>>>> 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. >>>>> Awasum >>>>> >>>>> On Wed, Mar 4, 2020 at 7:47 PM Yemdjih Kaze Nasser < >>>>> kazenas...@gmail.com> wrote: >>>>> >>>>>> 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 existence of duplicate values for some >>>>>> unique entries in the database. >>>>>> >>>>>> I don't know if anyone else is experiencing this. Perhaps >>>>>> someone/anyone can check and provide feedback. Maybe the problem is on my >>>>>> end and OS but I got to check. >>>>>> >>>>>> Thanks >>>>>> >>>>> >>> >>> -- >>> >>> Saransh Sharma >>> *Research Partner* >>> *Muellner Internet Pvt Ltd * >>> >>> >>> ---------------------------------------------------------------------------------------------- >>> >>> The idea of separation of me and you is amazing. >>> >>> ---------------------------------------------------------------------------------------------- >>> *Company Website <https://www.muellners.com/> **Company Linkedin >>> <https://www.linkedin.com/company/muellners> * >>> Company Facebook <https://www.facebook.com/muellners> >>> >>> This mail is governed by Muellner® Internet Private Limited's IT >>> policy. >>> The information contained in this e-mail and any accompanying documents >>> may contain information that is confidential or otherwise protected from >>> disclosure. If you are not the intended recipient of this message, or if >>> this message has been addressed to you in error, please immediately alert >>> the sender by reply e-mail and then delete this message, including any >>> attachments. Any dissemination, distribution or other use of the contents >>> of this message by anyone other than the intended recipient is strictly >>> prohibited. All messages sent to and from this e-mail address may be >>> monitored as permitted by applicable law and regulations to ensure >>> compliance with our internal policies and to protect our business. E-mails >>> are not secure and cannot be guaranteed to be error free as they can be >>> intercepted, amended, lost or destroyed, or contain viruses. You are deemed >>> to have accepted these risks if you communicate with us by e-mail. >>> >> >> >> -- >> >> Saransh Sharma >> *Research Partner* >> *Muellner Internet Pvt Ltd * >> >> >> ---------------------------------------------------------------------------------------------- >> >> The idea of separation of me and you is amazing. >> >> ---------------------------------------------------------------------------------------------- >> *Company Website <https://www.muellners.com/> **Company Linkedin >> <https://www.linkedin.com/company/muellners> *Company Facebook >> <https://www.facebook.com/muellners> >> >> This mail is governed by Muellner® Internet Private Limited's IT policy. >> The information contained in this e-mail and any accompanying documents >> may contain information that is confidential or otherwise protected from >> disclosure. If you are not the intended recipient of this message, or if >> this message has been addressed to you in error, please immediately alert >> the sender by reply e-mail and then delete this message, including any >> attachments. Any dissemination, distribution or other use of the contents >> of this message by anyone other than the intended recipient is strictly >> prohibited. All messages sent to and from this e-mail address may be >> monitored as permitted by applicable law and regulations to ensure >> compliance with our internal policies and to protect our business. E-mails >> are not secure and cannot be guaranteed to be error free as they can be >> intercepted, amended, lost or destroyed, or contain viruses. You are deemed >> to have accepted these risks if you communicate with us by e-mail. >> > > > -- > > Saransh Sharma > *Research Partner* > *Muellner Internet Pvt Ltd * > > > ---------------------------------------------------------------------------------------------- > > The idea of separation of me and you is amazing. > > ---------------------------------------------------------------------------------------------- > *Company Website <https://www.muellners.com/> **Company Linkedin > <https://www.linkedin.com/company/muellners> *Company Facebook > <https://www.facebook.com/muellners> > > This mail is governed by Muellner® Internet Private Limited's IT policy. > The information contained in this e-mail and any accompanying documents > may contain information that is confidential or otherwise protected from > disclosure. If you are not the intended recipient of this message, or if > this message has been addressed to you in error, please immediately alert > the sender by reply e-mail and then delete this message, including any > attachments. Any dissemination, distribution or other use of the contents > of this message by anyone other than the intended recipient is strictly > prohibited. All messages sent to and from this e-mail address may be > monitored as permitted by applicable law and regulations to ensure > compliance with our internal policies and to protect our business. E-mails > are not secure and cannot be guaranteed to be error free as they can be > intercepted, amended, lost or destroyed, or contain viruses. You are deemed > to have accepted these risks if you communicate with us by e-mail. >
