[
https://issues.apache.org/jira/browse/ODE-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tammo van Lessen resolved ODE-611.
----------------------------------
Resolution: Not A Problem
This is known problem. Testing timing related classes, like our scheduler, is
always tricky. Either the test constraints are too tight, then you get an
error, or they you may miss when something is wrong. This error occurs only
from time to time when the machine is busy, which means for us that every thing
is okay. I know, it's a bit ugly, but we can live with that.
> Test Failed
> -----------
>
> Key: ODE-611
> URL: https://issues.apache.org/jira/browse/ODE-611
> Project: ODE
> Issue Type: Bug
> Components: Test environment
> Affects Versions: 2.0
> Environment: Debian / Linux apache Tomcat 5.5 Ode Trunk Rev. 777326
> Reporter: Christian Fonden
> Priority: Minor
> Fix For: 2.0
>
>
> The Following Unit Test fails:
> testParallelEnqueue
> Output Log is as follows:
> Running tests in ode:scheduler-simple
> Trying to override old definition of datatype junit
> [junit] Testsuite: org.apache.ode.scheduler.simple.JdbcDelegateTest
> [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 0.919 sec
> [junit] ------------- Standard Error -----------------
> [junit] log4j:WARN No appenders could be found for logger
> (org.apache.ode.scheduler.simple.JdbcDelegate).
> [junit] log4j:WARN Please initialize the log4j system properly.
> [junit] ------------- ---------------- ---------------
> [junit]
> [junit] Testcase: testGetNodeIds took 0.466 sec
> [junit] Testcase: testReassign took 0.024 sec
> [junit] Testcase: testScheduleImmediateTimeFilter took 0.029 sec
> [junit] Testcase: testScheduleImmediateMaxRows took 0.023 sec
> [junit] Testcase: testScheduleImmediateNodeFilter took 0.015 sec
> [junit] Testcase: testDeleteJob took 0.009 sec
> [junit] Testcase: testUpgrade took 0.226 sec
> [junit] Testsuite: org.apache.ode.scheduler.simple.RetriesTest
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 10.108 sec
> [junit]
> [junit] Testcase: testRetries took 10.088 sec
> [junit] Testsuite: org.apache.ode.scheduler.simple.SchedulerThreadTest
> [junit] Tests run: 3, Failures: 1, Errors: 0, Time elapsed: 3.371 sec
> [junit]
> [junit] Testcase: testSchedulingResolution took 0.602 sec
> [junit] Testcase: testStartStop took 0.705 sec
> [junit] Testcase: testParallelEnqueue took 2.012 sec
> [junit] FAILED
> [junit] null
> [junit] junit.framework.AssertionFailedError: null
> [junit] at
> org.apache.ode.scheduler.simple.SchedulerThreadTest.testParallelEnqueue(SchedulerThreadTest.java:94)
> [junit]
> [junit] TEST org.apache.ode.scheduler.simple.SchedulerThreadTest FAILED
> [junit] Testsuite: org.apache.ode.scheduler.simple.SimpleSchedulerTest
> [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 4.522 sec
> [junit]
> [junit] Testcase: testStartStop took 1.332 sec
> [junit] Testcase: testConcurrentExec took 0.313 sec
> [junit] Testcase: testImmediateScheduling took 0.218 sec
> [junit] Testcase: testNearFutureScheduling took 0.87 sec
> [junit] Testcase: testFarFutureScheduling took 0.866 sec
> [junit] Testcase: testRecovery took 0.407 sec
> [junit] Testcase: testRecoverySuppressed took 0.482 sec
> [junit] Tests FAILED
> The following tests failed:
> org.apache.ode.scheduler.simple.SchedulerThreadTest
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
