Thanks for the hint. I'll try it and let you know. Milinda
On Thu, Feb 26, 2009 at 5:20 PM, Tammo van Lessen <[email protected]>wrote: > Hi Milinda, > > could you run the test with "buildr compile test junit:report" or > similar and then check the /**/reports/junit/*.txt for anomalies (only > for the failing tests of course)? > > Thanks, > Tammo > > Milinda Pathirage wrote: > > Today I update the ODE_TRUNK and again ran the tests. But it gives me > > abnormal behavior. I ran tests 4 times. It gave different errors in 3 of > > those times. Here are part of the results: > > > > First Run: > > The following tests failed: > > org.apache.ode.test.StructuredActivities20Test > > > > > > > > Second Run onle axis2-war tests: > > =============================================== > > ode:axis2-war > > Total tests run: 5, Failures: 0, Skips: 0 > > =============================================== > > > > [Completed] Your build has completed: /home/milinda/Apache/ode_trunk > > buildr ode:axis2-war:test > > Completed in 6m40.338s > > > > > > > > > > Third Run: > > =============================================== > > ode:axis2-war > > Total tests run: 5, Failures: 1, Skips: 0 > > =============================================== > > > > The following tests failed: > > org.apache.ode.axis2.rampart.policy.SecuredServicesTest > > [Failed] Your build failed with an error: /home/milinda/Apache/ode_trunk: > > Tests failed! > > buildr aborted! > > Tests failed! > > > > (See full trace by running task with --trace) > > > > > > > > Fourth Run: > > 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.62 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.251 sec > > [junit] Testcase: testReassign took 0.015 sec > > [junit] Testcase: testScheduleImmediateTimeFilter took 0.016 sec > > [junit] Testcase: testScheduleImmediateMaxRows took 0.037 sec > > [junit] Testcase: testScheduleImmediateNodeFilter took 0.01 sec > > [junit] Testcase: testDeleteJob took 0.01 sec > > [junit] Testcase: testUpgrade took 0.209 sec > > [junit] Testsuite: org.apache.ode.scheduler.simple.RetriesTest > > [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 10.05 sec > > [junit] > > [junit] Testcase: testRetries took 10.046 sec > > [junit] Testsuite: > org.apache.ode.scheduler.simple.SchedulerThreadTest > > [junit] Tests run: 3, Failures: 1, Errors: 0, Time elapsed: 3.256 sec > > [junit] > > [junit] Testcase: testSchedulingResolution took 0.7 sec > > [junit] FAILED > > [junit] expected:<1> but was:<0> > > [junit] junit.framework.AssertionFailedError: expected:<1> but > was:<0> > > [junit] at > > > org.apache.ode.scheduler.simple.SchedulerThreadTest.testSchedulingResolution(SchedulerThreadTest.java:56) > > [junit] > > [junit] Testcase: testStartStop took 0.703 sec > > [junit] Testcase: testParallelEnqueue took 1.837 sec > > [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.491 sec > > [junit] > > [junit] Testcase: testStartStop took 1.315 sec > > [junit] Testcase: testConcurrentExec took 0.325 sec > > [junit] Testcase: testImmediateScheduling took 0.241 sec > > [junit] Testcase: testNearFutureScheduling took 0.871 sec > > [junit] Testcase: testFarFutureScheduling took 0.856 sec > > [junit] Testcase: testRecovery took 0.41 sec > > [junit] Testcase: testRecoverySuppressed took 0.461 sec > > [junit] Tests FAILED > > The following tests failed: > > org.apache.ode.scheduler.simple.SchedulerThreadTest > > [Failed] Your build failed with an error: /home/milinda/Apache/ode_trunk: > > Tests failed! > > buildr aborted! > > Tests failed! > > > > > > Second time I executed axis2-war tests only. That attempt was successful. > I > > think those test failures are not related to my fix in > SoapMessageconverter. > > I only changed SOAP header copying part. I have tested it with several > other > > BPELs which are not involve in SOAP header handling. > > > > Thanks, > > Milinda > > > > On Tue, Feb 24, 2009 at 11:02 AM, Milinda Pathirage < > > [email protected]> wrote: > > > >> I'll check it and let you know. > >> > >> Thanks, > >> Milinda > >> > >> > >> On Tue, Feb 24, 2009 at 4:31 AM, Alex Boisvert <[email protected] > >wrote: > >> > >>> Also, there was a time window in the past week where > >>> InstanceManagementTest > >>> failed. It's been fixed now so maybe an svn update is in order. > >>> > >>> alex > >>> > >>> > >>> On Mon, Feb 23, 2009 at 2:59 PM, Matthieu Riou < > [email protected] > >>>> wrote: > >>>> On Sat, Feb 21, 2009 at 3:40 AM, Milinda Pathirage < > >>>> [email protected]> wrote: > >>>> > >>>>> Does anyone know the reason for this: > >>>>> > >>>>> Couldn't find resource on the class path: testng.css > >>>>> The following tests failed: > >>>>> org.apache.ode.axis2.management.InstanceManagementTest > >>>>> rake aborted! > >>>>> Tests failed! > >>>>> > >>>>> There is a fix for SOAP Header handling in SoapMessageConverter. I > >>> can't > >>>>> commit it because tests were stopped due to above mentioned reason. > >>>>> > >>>> The css thing is just bogus, unrelated to the failure. For the test > >>> failure > >>>> itself, it seems to be working in other environments so I don't know > why > >>>> it's not for you and it's hard to diagnose without more information. > Are > >>>> you > >>>> sure the test doesn't fail because of your modifications? > >>>> > >>>> Matthieu > >>>> > >>>> > >>>>> > >>>>> Thanks, > >>>>> Milinda > >>>>> > >>>>> -- > >>>>> http://mpathirage.com > >>>>> http://wso2.org "Oxygen for Web Service Developers" > >>>>> http://wsaxc.blogspot.com "Web Services With Axis2/C" > >>>>> > >> > >> > >> -- > >> http://mpathirage.com > >> http://wso2.org "Oxygen for Web Service Developers" > >> http://wsaxc.blogspot.com "Web Services With Axis2/C" > >> > > > > > > > > > -- > Tammo van Lessen - http://www.taval.de > -- http://mpathirage.com http://wso2.org "Oxygen for Web Service Developers" http://wsaxc.blogspot.com "Web Services With Axis2/C"
