Hi Gandhi, I suggest you remove /tmp/ctakes-*.
No I did not change anything, as Jenkins is starting with clean environment every single time. Alex On Sat, Nov 18, 2017 at 4:51 PM, Gandhi Rajan Natarajan < [email protected]> wrote: > Hi Alex, > > I tried out a fresh checkout from SVN and git. Tried a full build in both > setups and DateAnnotatorTest fails consistently for me. Did you changed > build order or something in pom to fix it? > > Regards, > Gandhi > > > -----Original Message----- > From: Gandhi Rajan Natarajan [mailto:[email protected]] > Sent: Sunday, November 19, 2017 2:47 AM > To: [email protected] > Subject: RE: YTEX Assistance required RE: Test case failure [EXTERNAL] > > Thanks for the info Alex. Will check and keep you posted. > > Regards, > Gandhi > > > -----Original Message----- > From: Alexandru Zbarcea [mailto:[email protected]] > Sent: Sunday, November 19, 2017 2:29 AM > To: Apache cTAKES Dev <[email protected]> > Subject: Re: YTEX Assistance required RE: Test case failure [EXTERNAL] > > Hi Gandhi, > > I saw the same thing on the cTAKES-trunk-Java-1.8 build #38 [1]. I also > encountered the issue few times, and is very inconsistent, without being > able to track it down. > > It seems that ytexDates.iterator() is empty in certain conditions. I think > is related to the order of executions and how resources are generated. On > the last builds I couldn't reproduce it. > > So I suggest a full: > mvn clean install > > Alex > > [1] - > https://builds.apache.org/view/C/view/Apache%20cTAKES/ > job/cTAKES-trunk-Java-1.8/38/org.apache.ctakes$ctakes-ytex- > uima/testReport/org.apache.ctakes.ytex.uima.annotators/DateAnnotatorTest/ > testParseDate/ > > > On Sat, Nov 18, 2017 at 12:11 PM, Finan, Sean < > [email protected]> wrote: > > > Is anybody that was involved with ytex still out there? > > > > -----Original Message----- > > From: Gandhi Rajan Natarajan [mailto:[email protected]] > > Sent: Saturday, November 18, 2017 9:53 AM > > To: [email protected] > > Subject: Test case failure [EXTERNAL] > > > > Hi All, > > > > I did a fresh check out of cTAKES code from SVN to work on Spring > > upgrade patch. But I have one failed test case in ctakes-ytex-uima > > module. The error trace is as follows, > > > > ------------------------------------------------------------ > > ------------------- > > Test set: org.apache.ctakes.ytex.uima.annotators.DateAnnotatorTest > > ------------------------------------------------------------ > > ------------------- > > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.583 > > sec <<< FAILURE! > > testParseDate(org.apache.ctakes.ytex.uima.annotators.DateAnnotatorTest > > ) > > Time elapsed: 0.547 sec <<< FAILURE! > > java.lang.AssertionError > > at org.junit.Assert.fail(Assert.java:86) > > at org.junit.Assert.assertTrue(Assert.java:41) > > at org.junit.Assert.assertTrue(Assert.java:52) > > at org.apache.ctakes.ytex.uima. > > annotators.DateAnnotatorTest.testParseDate(DateAnnotatorTest.java:54) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > > Method) > > at sun.reflect.NativeMethodAccessorImpl.invoke( > > NativeMethodAccessorImpl.java:62) > > at sun.reflect.DelegatingMethodAccessorImpl.invoke( > > DelegatingMethodAccessorImpl.java:43) > > at java.lang.reflect.Method.invoke(Method.java:498) > > at org.junit.runners.model.FrameworkMethod$1. > > runReflectiveCall(FrameworkMethod.java:47) > > at org.junit.internal.runners. > > model.ReflectiveCallable.run(ReflectiveCallable.java:12) > > at org.junit.runners.model.FrameworkMethod. > > invokeExplosively(FrameworkMethod.java:44) > > at org.junit.internal.runners.statements.InvokeMethod. > > evaluate(InvokeMethod.java:17) > > at org.junit.runners.ParentRunner.runLeaf( > > ParentRunner.java:271) > > at org.junit.runners.BlockJUnit4ClassRunner.runChild( > > BlockJUnit4ClassRunner.java:70) > > at org.junit.runners.BlockJUnit4ClassRunner.runChild( > > BlockJUnit4ClassRunner.java:50) > > at org.junit.runners.ParentRunner$3.run( > > ParentRunner.java:238) > > at org.junit.runners.ParentRunner$1.schedule( > > ParentRunner.java:63) > > at org.junit.runners.ParentRunner.runChildren( > > ParentRunner.java:236) > > at org.junit.runners.ParentRunner.access$000( > > ParentRunner.java:53) > > at org.junit.runners.ParentRunner$2.evaluate( > > ParentRunner.java:229) > > at org.junit.runners.ParentRunner.run(ParentRunner. > > java:309) > > at org.apache.maven.surefire. > > junit4.JUnit4Provider.execute(JUnit4Provider.java:249) > > at org.apache.maven.surefire.junit4.JUnit4Provider. > > executeTestSet(JUnit4Provider.java:142) > > at > > org.apache.maven.surefire.junit4.JUnit4Provider.invoke( > > JUnit4Provider.java:113) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > > Method) > > at sun.reflect.NativeMethodAccessorImpl.invoke( > > NativeMethodAccessorImpl.java:62) > > at sun.reflect.DelegatingMethodAccessorImpl.invoke( > > DelegatingMethodAccessorImpl.java:43) > > at java.lang.reflect.Method.invoke(Method.java:498) > > at org.apache.maven.surefire.util.ReflectionUtils. > > invokeMethodWithArray(ReflectionUtils.java:189) > > at org.apache.maven.surefire.booter.ProviderFactory$ > > ProviderProxy.invoke(ProviderFactory.java:165) > > at org.apache.maven.surefire.booter.ProviderFactory. > > invokeProvider(ProviderFactory.java:85) > > at org.apache.maven.surefire.booter.ForkedBooter. > > runSuitesInProcess(ForkedBooter.java:104) > > at org.apache.maven.surefire.booter.ForkedBooter.main( > > ForkedBooter.java:75) > > > > Am I missing something or is it broken recently? > > > > Regards, > > Gandhi > > > > This email and any files transmitted with it are confidential and > > intended solely for the use of the individual or entity to whom they are > addressed. > > If you are not the named addressee you should not disseminate, > > distribute or copy this e-mail. Please notify the sender or system > > manager by email immediately if you have received this e-mail by > > mistake and delete this e-mail from your system. If you are not the > > intended recipient you are notified that disclosing, copying, > > distributing or taking any action in reliance on the contents of this > > information is strictly prohibited and against the law. > > > This email and any files transmitted with it are confidential and intended > solely for the use of the individual or entity to whom they are addressed. > If you are not the named addressee you should not disseminate, distribute > or copy this e-mail. Please notify the sender or system manager by email > immediately if you have received this e-mail by mistake and delete this > e-mail from your system. If you are not the intended recipient you are > notified that disclosing, copying, distributing or taking any action in > reliance on the contents of this information is strictly prohibited and > against the law. > This email and any files transmitted with it are confidential and intended > solely for the use of the individual or entity to whom they are addressed. > If you are not the named addressee you should not disseminate, distribute > or copy this e-mail. Please notify the sender or system manager by email > immediately if you have received this e-mail by mistake and delete this > e-mail from your system. If you are not the intended recipient you are > notified that disclosing, copying, distributing or taking any action in > reliance on the contents of this information is strictly prohibited and > against the law. >
