[
https://issues.apache.org/jira/browse/DERBY-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-4356:
---------------------------------
Attachment: z.diff
Attaching z.diff. This adds a dummy script class, ZSuite which is useful for
reproducing instances of this bug. To use this class:
1) Apply the patch
2) Edit ZSuite to replace ClassLoaderBootTest with whatever upstream test has
left the cruft which is causing these downstream diffs.
3) Run the script like so:
java -Xmx512m junit.textui.TestRunner
org.apache.derbyTesting.functionTests.tests.management.ZSuite
> testStartStopManagementFromApplication(org.apache.derbyTesting.functionTests.tests.management.ManagementMBeanTest)junit.framework.AssertionFailedError:
> expected:<2> but was:<%>
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4356
> URL: https://issues.apache.org/jira/browse/DERBY-4356
> Project: Derby
> Issue Type: Bug
> Components: JMX, Test
> Affects Versions: 10.4.3.0, 10.5.3.1, 10.6.0.0
> Environment: All
> Reporter: Ole Solberg
> Attachments: z.diff
>
>
> Seen with svn r805448 on tinderbox/trunk (
> http://dbtg.foundry.sun.com/derby/test/tinderbox_trunk16/jvm1.6/testing/Limited/index.html
> ).
> See e.g.
> http://dbtg.foundry.sun.com/derby/test/tinderbox_trunk16/jvm1.6/testing/Limited/testSummary-805576.html
> ,
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-805470.html
> .
> The failure signature is
> testStartStopManagementFromApplication(org.apache.derbyTesting.functionTests.tests.management.ManagementMBeanTest)junit.framework.AssertionFailedError:
> expected:<2> but was:<14>
> at
> org.apache.derbyTesting.functionTests.tests.management.ManagementMBeanTest.startStopManagement(ManagementMBeanTest.java:86)
> at
> org.apache.derbyTesting.functionTests.tests.management.ManagementMBeanTest.testStartStopManagementFromApplication(ManagementMBeanTest.java:56)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at
> org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:109)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> at junit.extensions.TestSetup.run(TestSetup.java:25)
> at
> org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> at junit.extensions.TestSetup.run(TestSetup.java:25)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> at junit.extensions.TestSetup.run(TestSetup.java:25)
> at
> org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> This seems to be a similar failure signature as for DERBY-3561 and
> DERBY-3499. I choose to create a new issue for the new occurrences.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
