Uploaded image for project: 'MyCoRe'
  1. MCR-1493

MCRProcessableFactoryTest depends on execution speed

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: 2016.12
    • Fix Version/s: 2017.05
    • Component/s: mycore-base
    • Labels:
    • Sprint:

      Description

      Running org.mycore.util.concurrent.processing.MCRProcessableFactoryTest
      Setting MCR.Home=/tmp/junit4981046312153565223/mcrhome
      Setting MCR.AppName=mycore-base
      Creating config directory: /tmp/junit4981046312153565223/mcrhome/mycore-base
      MyCoRe components detected: mcr:mycore-base
      Applications modules detected: 'none'
      MCRConfigurationInputStream.getMyCoRePropertiesInstance Current configuration directory: /tmp/junit4981046312153565223/mcrhome/mycore-base 
      Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.919 sec <<< FAILURE! - in org.mycore.util.concurrent.processing.MCRProcessableFactoryTest
      newPool(org.mycore.util.concurrent.processing.MCRProcessableFactoryTest)  Time elapsed: 0.993 sec  <<< FAILURE!
      java.lang.AssertionError
      	at org.mycore.util.concurrent.processing.MCRProcessableFactoryTest.newPool(MCRProcessableFactoryTest.java:44)
      

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                yagee Thomas Scheffler
                Reporter:
                yagee Thomas Scheffler
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: