Community
Participate
Working Groups
Build Identifier: CDO Model Repository SDK 4.0.0.v20110831-1303 org.eclipse.emf.cdo.sdk.feature.group In legacy mode, with CDOTransaction.options().addChangeSubscriptionPolicy(CDOAdapterPolicy.ALL) set, on commit of a new legacy object added, the remote clients receives a CDODeltaNotification with newValue instanceof CDOLegacyWrapper Reproducible: Always
Created attachment 204596 [details] A fix which call getEObject() to get the wrapped object
Created attachment 204603 [details] second release of the fix to fix getOldValue()
Created attachment 204604 [details] A patch of the Bugzilla_355915_Test to test these cases
Hi Esteban, thanks for the patch. But somehow it seems to be outdated. I cannot apply it neither non head nor on the maintenance branch. Could you please update it? Thanks.
Just to avoid confusions: I meant the test, not the fix ;)
Created attachment 204651 [details] The complete test case Hi, I hava attached the complete test case to avoid conflict on patch application.
Created attachment 204824 [details] Test v1 Hi Esteban, thanks for the test. I attached it as patch and renamed it to make align it with the bug number.
Created attachment 204825 [details] Test v1 Mixed test and fix. This is the test.
Created attachment 204826 [details] Patch v1 And here comes the patch. I changed it a bit and moved the conversion to the adapt method.
Assuming 4.1
Correct assumption. I'll provide a bug for 4.0 maintenance as soon as HEAD is fixed.
Created attachment 204831 [details] Patch v2 (incl. test) I removed the reference to the test for bug 359669 that does not compile. Executing tests...
All tests pass. Good work!
Committed revision 9467
And revision 9468 ;-)
Hudson tests keep failing (in legacy scenarios) with: junit.framework.AssertionFailedError: expected:<true> but was:<false> at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:283) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:143) at junit.framework.Assert.assertEquals(Assert.java:149) at org.eclipse.emf.cdo.tests.bugzilla.Bugzilla_359992_Test.testDeltaNotification(Bugzilla_359992_Test.java:140) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:168) at org.eclipse.net4j.util.tests.AbstractOMTest.runBare(AbstractOMTest.java:218) at org.eclipse.emf.cdo.tests.config.impl.ConfigTest.runBare(ConfigTest.java:526) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at org.eclipse.net4j.util.tests.AbstractOMTest.run(AbstractOMTest.java:264) at junit.framework.TestSuite.runTest(TestSuite.java:243) at org.eclipse.emf.cdo.tests.config.impl.ConfigTestSuite$TestWrapper.runTest(ConfigTestSuite.java:119) at junit.framework.TestSuite.run(TestSuite.java:238) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) Please investigate
Eike, the patch was committed on 9th october and build #1884 passed on 10th. As far as I remember this test failed several times before, so I do not think that there is a direct relationship between the test failure in this bug. I think we should open a new bug for this issue as it seems that legacy might have a general problem with delta notification or worse: There is a timing issue related to delta notifications.
I'm not sure about that. The test outcome depends on timing (timeouts) and that's always a little indeterministic.
Ah. I did not recognize that the failing build was due to the test of this bug. I thought it was a test method from another test. It might be a small mistake in the test logic (Should block until the notifier was notified).
Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.
Hi Christian, I assign this legacy mode zilla to you, just in case you're ineterested. Don't feel obliged ;-)
We'll try to address open problems in 4.3 (master) first and then port fixes back to 4.2.
Moving all open bugzillas to 4.5.
Moving all unaddressed bugzillas to 4.6.
Moving all open bugs to 4.7
Moving all unresolved issues to version 4.8-
Moving all unresolved issues to version 4.9
Moving to 4.13.