You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (Jira)" <de...@uima.apache.org> on 2020/05/14 10:18:00 UTC

[jira] [Created] (UIMA-6233) Failing unit tests depending on test execution order

Richard Eckart de Castilho created UIMA-6233:
------------------------------------------------

             Summary: Failing unit tests depending on test execution order
                 Key: UIMA-6233
                 URL: https://issues.apache.org/jira/browse/UIMA-6233
             Project: UIMA
          Issue Type: Improvement
          Components: Ruta
            Reporter: Richard Eckart de Castilho
            Assignee: Richard Eckart de Castilho
             Fix For: 2.8.2ruta


There are two tests which fail on some systems but not on all (most):

*org.apache.uima.ruta.NewCASPipelineTest.test*
{code}
org.apache.uima.UIMARuntimeException: 
Illegal adding of additional MetaData after CASes have been defined.
  file:/var/lib/jenkins/jobs/EntwicklerTeam/jobs/content/jobs/uima/jobs/ruta-v2-default-build/workspace/ruta-core/target/classes/org/apache/uima/ruta/engine/BasicEngine.xml
  Likely cause is the reuse of a Resource Manager object for a different pipeline, after it has already been initialized.
	at org.apache.uima.ruta.NewCASPipelineTest.createAE(NewCASPipelineTest.java:63)
	at org.apache.uima.ruta.NewCASPipelineTest.test(NewCASPipelineTest.java:70)
{code}

*org.apache.uima.ruta.ConflictingTypeTest.test*
{code}
org.apache.uima.UIMARuntimeException: 
Illegal adding of additional MetaData after CASes have been defined.
  file:/var/lib/jenkins/jobs/EntwicklerTeam/jobs/content/jobs/uima/jobs/ruta-v2-default-build/workspace/ruta-core/target/classes/org/apache/uima/ruta/engine/BasicEngine.xml
  Likely cause is the reuse of a Resource Manager object for a different pipeline, after it has already been initialized.
	at org.apache.uima.ruta.ConflictingTypeTest.createAE(ConflictingTypeTest.java:56)
	at org.apache.uima.ruta.ConflictingTypeTest.test(ConflictingTypeTest.java:63)
{code}

My guess: some test sets a {{ResourceManagerCreator}} to create a singleton resource manager and depending on the order in which the tests are executed, this sometimes causes tests to fail and other times not.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)