uima-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Burn Lewis <burnle...@gmail.com>
Subject Re: C-Groups status remains off in web server after installing C-Groups
Date Fri, 09 Oct 2015 20:56:55 GMT
Satya,

Unfortunately the stack trace printed by the code is apparently hidden.
What svn revision level of DUCC did you check-out  There was a bug in the
svn code for a few hours recently so you may have been unlucky and got that
level.  Unless you need some of our recent fixes I'd suggest staying with
the source for 2.0.0.  We have started testing a 2.0.1 release that fixes a
few annoying bugs.

~Burn

On Wed, Oct 7, 2015 at 12:39 AM, Satya Nand Kanodia <
satya.kanodia@orkash.com> wrote:

> Dear Burn,
>
> failure occurs every time I run test cases.
>
> This was in the log file
> uima-ducc-trunk/uima-ducc-orchestrator/target/surefire-reports/org.apache.uima.ducc.orchestrator.jd.scheduler.test.TestSuite.txt
>
>
> -------------------------------------------------------------------------------
> Test set: org.apache.uima.ducc.orchestrator.jd.scheduler.test.TestSuite
>
> -------------------------------------------------------------------------------
> Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.752 sec
> <<< FAILURE! - in
> org.apache.uima.ducc.orchestrator.jd.scheduler.test.TestSuite
> testJdReservation(org.apache.uima.ducc.orchestrator.jd.scheduler.test.TestSuite)
> Time elapsed: 0.639 sec  <<< FAILURE!
> java.lang.AssertionError:
>     at org.junit.Assert.fail(Assert.java:91)
>     at
> org.apache.uima.ducc.orchestrator.jd.scheduler.test.TestSuite.ducc_config(TestSuite.java:81)
>     at
> org.apache.uima.ducc.orchestrator.jd.scheduler.test.TestSuite.before(TestSuite.java:61)
>
> testJdSchedulerStatic(org.apache.uima.ducc.orchestrator.jd.scheduler.test.TestSuite)
> Time elapsed: 0.007 sec  <<< FAILURE!
> java.lang.AssertionError:
>     at org.junit.Assert.fail(Assert.java:91)
>     at
> org.apache.uima.ducc.orchestrator.jd.scheduler.test.TestSuite.ducc_config(TestSuite.java:81)
>     at
> org.apache.uima.ducc.orchestrator.jd.scheduler.test.TestSuite.before(TestSuite.java:61)
>
> testJdSchedulerDynamic(org.apache.uima.ducc.orchestrator.jd.scheduler.test.TestSuite)
> Time elapsed: 0.009 sec  <<< FAILURE!
> java.lang.AssertionError:
>     at org.junit.Assert.fail(Assert.java:91)
>     at
> org.apache.uima.ducc.orchestrator.jd.scheduler.test.TestSuite.ducc_config(TestSuite.java:81)
>     at
> org.apache.uima.ducc.orchestrator.jd.scheduler.test.TestSuite.before(TestSuite.java:61)
>
> Thanks and Regards,
> Satya Nand Kanodia
>
> On 10/07/2015 03:09 AM, Burn Lewis wrote:
>
>> re: Test failures
>> Details about the failure should be earlier in the log.  Chances are it's
>> an intermittent problem, perhaps caused by a network glitch.  If it
>> re-occurs please post the details.
>>
>> ~Burn
>>
>> On Tue, Oct 6, 2015 at 11:10 AM, Jim Challenger <challngr@gmail.com>
>> wrote:
>>
>> Satya,
>>>       Did you get a clean build?  You'd expect to see something like
>>> this:
>>> [INFO] uima-ducc-parent .................................. SUCCESS [
>>> 7.309 s]
>>> [INFO] Apache UIMA DUCC: uima-ducc-user .................. SUCCESS [
>>> 6.986 s]
>>> [INFO] Apache UIMA DUCC: uima-ducc-common ................ SUCCESS [
>>> 6.018 s]
>>> [INFO] Apache UIMA DUCC: uima-ducc-container ............. SUCCESS [
>>> 3.725 s]
>>> [INFO] Apache UIMA DUCC: uima-ducc-transport ............. SUCCESS [
>>> 5.739 s]
>>> [INFO] Apache UIMA DUCC: uima-ducc-cli ................... SUCCESS [
>>> 3.354 s]
>>> [INFO] Apache UIMA DUCC: uima-ducc-pm .................... SUCCESS [
>>> 1.672 s]
>>> [INFO] Apache UIMA DUCC: uima-ducc-rm .................... SUCCESS [
>>> 2.348 s]
>>> [INFO] Apache UIMA DUCC: uima-ducc-sm .................... SUCCESS [
>>> 2.124 s]
>>> [INFO] Apache UIMA DUCC: uima-ducc-database .............. SUCCESS [
>>> 2.182 s]
>>> [INFO] Apache UIMA DUCC: uima-ducc-orchestrator .......... SUCCESS [
>>> 2.915 s]
>>> [INFO] Apache UIMA DUCC: uima-ducc-agent ................. SUCCESS [
>>> 2.447 s]
>>> */[INFO] uima-ducc-duccdocs ................................ SUCCESS [
>>> 19.870 s]/*
>>> [INFO] Apache UIMA DUCC: uima-ducc-web ................... SUCCESS [
>>> 3.596 s]
>>> [INFO] Apache UIMA DUCC: uima-ducc-examples .............. SUCCESS [
>>> 2.502 s]
>>> [INFO] uima-ducc-spawn ................................... SUCCESS [
>>> 0.432 s]
>>> [INFO] Apache UIMA-DUCC: uima-ducc ....................... SUCCESS [
>>> 53.761 s]
>>>
>>> In particular, the success of uima-ducc-duccdocs, which will usually take
>>> longer than the other subprojects if it's actually doing something.
>>>
>>> if so, can you check in uima-ducc-ducdocs/target/site to see if things
>>> are
>>> there?   You'd expect to see three directories, one with html, one with
>>> pdf, and the standalone install section.
>>>
>>> Jim
>>>
>>>
>>> On 10/6/15 12:49 AM, Satya Nand Kanodia wrote:
>>>
>>> Dear Eddie,
>>>>
>>>> Thank you :)
>>>>
>>>> It solved the issue. I was using DUCC 1.1 documentation to install
>>>> C-Groups because I did not have v2.1 documentation .
>>>>
>>>> I cloned DUCC v2.1 form git-hub and tried to built it, It failed at
>>>> executing test cases. It gave below exception.
>>>>
>>>> Failed to execute goal
>>>> org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test)
>>>> on
>>>> project uima-ducc-orchestrator: There are test failures.
>>>>
>>>>
>>>> After that I tried to build it with mvn clean install -DskipTests. It
>>>> was
>>>> a success. Then acording to README file , for building
>>>> documentation I executed mvn clean install -Pbuild-duccdocs -DskipTests.
>>>> It worked, But there was no duccbook.
>>>>
>>>> After installing DUCC 2.1 from binary when I click onDuccBook on
>>>> webserver,I got following error.
>>>>
>>>> HTTP ERROR: 404
>>>>
>>>> Problem accessing /doc/duccbook.html. Reason:
>>>>
>>>>      Not Found
>>>>
>>>>
>>>> Thanks and Regards,
>>>> Satya Nand Kanodia
>>>>
>>>> On 10/05/2015 07:01 PM, Eddie Epstein wrote:
>>>>
>>>> 0 made a small change in cgconfig.conf, adding two lines to enable
>>>>>
>>>>>
>>>>
>>>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message