[jira] [Commented] (JDO-767) JDO TCK lifecycle tests fail
[ https://issues.apache.org/jira/browse/JDO-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272251#comment-16272251 ] Andy Jefferson commented on JDO-767: Linux 64-bit (kernel 4.9.56), OpenJDK JVM (1.8.0.141), with 8Gb RAM. Differences can also highlight with garbage collection and L1/L2 caching, hence why I mention the RAM. > JDO TCK lifecycle tests fail > > > Key: JDO-767 > URL: https://issues.apache.org/jira/browse/JDO-767 > Project: JDO > Issue Type: Bug > Components: tck >Affects Versions: JDO 3.1 >Reporter: Craig L Russell >Assignee: Tilmann Zäschke > Fix For: JDO 3.2 > > > cat dsid-lifecycle-tck.txt > 10:14:11,507 (main) INFO [org.apache.jdo.tck] - Exception during setUp or > runtest: > junit.framework.AssertionFailedError: > Assertion A5.6.2-6 (NontransactionalWriteDatastoreRollback) failed: after > datastore rollback > expected: 100 > actual: 999 > at junit.framework.Assert.fail(Assert.java:47) > at org.apache.jdo.tck.JDO_Test.failOnError(JDO_Test.java:1245) > at > org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreRollback.testDatastoreRollback(NontransactionalWriteDatastoreRollback.java:87) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at junit.framework.TestCase.runTest(TestCase.java:154) > at org.apache.jdo.tck.JDO_Test.runBare(JDO_Test.java:284) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at junit.textui.TestRunner.doRun(TestRunner.java:116) > at > org.apache.jdo.tck.util.BatchTestRunner.doRun(BatchTestRunner.java:108) > at > org.apache.jdo.tck.util.BatchTestRunner.start(BatchTestRunner.java:148) > at > org.apache.jdo.tck.util.BatchTestRunner.main(BatchTestRunner.java:123) > 10:14:11,527 (main) INFO [org.apache.jdo.tck] - Exception during setUp or > runtest: > junit.framework.AssertionFailedError: > Assertion A5.6.2-4 (NontransactionalWriteDatastoreCommitConflict) failed: > after datastore commit with conflict > expected: 999 > actual: 555 > at junit.framework.Assert.fail(Assert.java:47) > at org.apache.jdo.tck.JDO_Test.failOnError(JDO_Test.java:1245) > at > org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreCommitConflict.testDatastoreCommitConflict(NontransactionalWriteDatastoreCommitConflict.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at junit.framework.TestCase.runTest(TestCase.java:154) > at org.apache.jdo.tck.JDO_Test.runBare(JDO_Test.java:284) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at junit.textui.TestRunner.doRun(TestRunner.java:116) > at > org.apache.jdo.tck.util.BatchTestRunner.doRun(BatchTestRunner.java:108) > at > org.apache.jdo.tck.util.BatchTestRunner.start(BatchTestRunner.java:148) > at > org.apache.jdo.tck.util.BatchTestRunner.main(BatchTestRunner.java:123) > 10:14:11,532 (main) INFO [org.apache.jdo.tck] - Exception during setUp or > runtest: > junit.framework.AssertionFailedError: > Assertion A5.6.2-10 (NontransactionalWriteOptimisticRollback) failed: after > optimistic rollback > expected: 100 > actual: 999 > at junit.framework.Assert.fail(Assert.java:47) > at org.apache.jdo.tck.JDO_Test.failOnError(JDO_Test.java:1245) > at >
[jira] [Commented] (JDO-767) JDO TCK lifecycle tests fail
[ https://issues.apache.org/jira/browse/JDO-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271696#comment-16271696 ] Tilmann Zäschke commented on JDO-767: - So it looks like we have three people (Craig, Michael and myself) who have trouble getting this to work. Myself, I tried three separate checkouts on two different machines. They were all Windows 10 with Java 8 though. Michael used Mac and Java 8, I'm not sure what Craig used. It looks like it's at least easy to get the set-up wrong. @Andy Sorry, could you tell us a bit about your set-up? Are you maybe on Linux? Oracle Java? This really shouldn't make a difference but in my experience it sometimes does... > JDO TCK lifecycle tests fail > > > Key: JDO-767 > URL: https://issues.apache.org/jira/browse/JDO-767 > Project: JDO > Issue Type: Bug > Components: tck >Affects Versions: JDO 3.1 >Reporter: Craig L Russell >Assignee: Tilmann Zäschke > Fix For: JDO 3.2 > > > cat dsid-lifecycle-tck.txt > 10:14:11,507 (main) INFO [org.apache.jdo.tck] - Exception during setUp or > runtest: > junit.framework.AssertionFailedError: > Assertion A5.6.2-6 (NontransactionalWriteDatastoreRollback) failed: after > datastore rollback > expected: 100 > actual: 999 > at junit.framework.Assert.fail(Assert.java:47) > at org.apache.jdo.tck.JDO_Test.failOnError(JDO_Test.java:1245) > at > org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreRollback.testDatastoreRollback(NontransactionalWriteDatastoreRollback.java:87) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at junit.framework.TestCase.runTest(TestCase.java:154) > at org.apache.jdo.tck.JDO_Test.runBare(JDO_Test.java:284) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at junit.textui.TestRunner.doRun(TestRunner.java:116) > at > org.apache.jdo.tck.util.BatchTestRunner.doRun(BatchTestRunner.java:108) > at > org.apache.jdo.tck.util.BatchTestRunner.start(BatchTestRunner.java:148) > at > org.apache.jdo.tck.util.BatchTestRunner.main(BatchTestRunner.java:123) > 10:14:11,527 (main) INFO [org.apache.jdo.tck] - Exception during setUp or > runtest: > junit.framework.AssertionFailedError: > Assertion A5.6.2-4 (NontransactionalWriteDatastoreCommitConflict) failed: > after datastore commit with conflict > expected: 999 > actual: 555 > at junit.framework.Assert.fail(Assert.java:47) > at org.apache.jdo.tck.JDO_Test.failOnError(JDO_Test.java:1245) > at > org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreCommitConflict.testDatastoreCommitConflict(NontransactionalWriteDatastoreCommitConflict.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at junit.framework.TestCase.runTest(TestCase.java:154) > at org.apache.jdo.tck.JDO_Test.runBare(JDO_Test.java:284) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at junit.textui.TestRunner.doRun(TestRunner.java:116) > at > org.apache.jdo.tck.util.BatchTestRunner.doRun(BatchTestRunner.java:108) > at > org.apache.jdo.tck.util.BatchTestRunner.start(BatchTestRunner.java:148) > at > org.apache.jdo.tck.util.BatchTestRunner.main(BatchTestRunner.java:123) > 10:14:11,532 (main) INFO [org.apache.jdo.tck] - Exception during setUp or > runtest: > junit.framework.AssertionFailedError: >
[jira] [Comment Edited] (JDO-767) JDO TCK lifecycle tests fail
[
https://issues.apache.org/jira/browse/JDO-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271531#comment-16271531
]
Michael Bouschen edited comment on JDO-767 at 11/29/17 9:02 PM:
I checked out a new workspace and switched to DN version 5.1.5-SNAPSHOT
(version Nov 29, 2017). I'm running the TCK on a mac, with mvn 3.3.9 and jdk
1.8.0_151.
I get the following test failures:
{noformat}
dsid-lifecycle-junit.txt:
** Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0
app-lifecycle-junit.txt:
** Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0
{noformat}
Details see below.
I also see the following exception in dsid-lifecycle-jdori.txt and
app-lifecycle-jdori.txt. I have no idea whether this is related to the test
failures:
{noformat}
ERROR [DataNucleus.MetaData] - Class
org.apache.jdo.tck.pc.compositeAnnotation.ApplicationIdDiscriminatorClassName
has application-identity and no objectid-class specified yet has 0 primary key
fields.
Unable to use SingleFieldIdentity.
{noformat}
Here are the details of the test failures. They look the same as the ones Craig
desribes above:
{noformat}
1)
testDatastoreRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreRollback)junit.framework.AssertionFailedError:
Assertion A5.6.2-6 (NontransactionalWriteDatastoreRollback) failed: after
datastore rollback
expected: 100
actual: 999
2)
testDatastoreCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreCommitConflict)junit.framework.AssertionFailedError:
Assertion A5.6.2-4 (NontransactionalWriteDatastoreCommitConflict) failed: after
datastore commit with conflict
expected: 999
actual: 555
3)
testOptimisticRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticRollback)junit.framework.AssertionFailedError:
Assertion A5.6.2-10 (NontransactionalWriteOptimisticRollback) failed: after
optimistic rollback
expected: 100
actual: 999
4)
testOptimisticCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticCommitConflict)junit.framework.AssertionFailedError:
Assertion A5.6.2-8 (NontransactionalWriteOptimisticCommitConflict) failed:
after optimistic commit with conflicttransaction succeeded but should not
succeed.
5)
test(org.apache.jdo.tck.lifecycle.StateTransitions)junit.framework.AssertionFailedError:
Assertions A5.9-1 through A5.9-190 (StateTransitions) failed:
StateTransitions: no transaction; current state persistent-nontransactional
write field outside tx transitioned instance to invalid state hollow; expected
state persistent-nontransactional-dirty
{noformat}
was (Author: mbo):
I checked out a new workspace and switched to DN version 5.1.5-SNAPSHOT
(version Nov 29, 2017). I'm running the TCK on a mac, with mvn 3.3.9 and jdk
1.8.0_151.
I get the following test failures:
{noformat}
dsid-lifecycle-junit.txt:
** Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0
app-lifecycle-junit.txt:
** Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0
{noformat}
Details see below.
I also see the following exception in dsid-lifecycle-jdori.txt and
app-lifecycle-jdori.txt. I have no idea whether this is related to the test
failures:
{noformat}
ERROR [DataNucleus.MetaData] - Class
org.apache.jdo.tck.pc.compositeAnnotation.ApplicationIdDiscriminatorClassName
has application-identity and no objectid-class specified yet has 0 primary key
fields. Unable to use SingleFieldIdentity.
{noformat}
Here are the details of the test failures. They look the same as the ones Craig
desribes above:
{noformat}
1)
testDatastoreRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreRollback)junit.framework.AssertionFailedError:
Assertion A5.6.2-6 (NontransactionalWriteDatastoreRollback) failed: after
datastore rollback
expected: 100
actual: 999
2)
testDatastoreCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreCommitConflict)junit.framework.AssertionFailedError:
Assertion A5.6.2-4 (NontransactionalWriteDatastoreCommitConflict) failed: after
datastore commit with conflict
expected: 999
actual: 555
3)
testOptimisticRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticRollback)junit.framework.AssertionFailedError:
Assertion A5.6.2-10 (NontransactionalWriteOptimisticRollback) failed: after
optimistic rollback
expected: 100
actual: 999
4)
testOptimisticCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticCommitConflict)junit.framework.AssertionFailedError:
Assertion A5.6.2-8 (NontransactionalWriteOptimisticCommitConflict) failed:
after optimistic commit with conflicttransaction succeeded but should not
succeed.
5)
test(org.apache.jdo.tck.lifecycle.StateTransitions)junit.framework.AssertionFailedError:
Assertions A5.9-1 through A5.9-190 (StateTransitions) failed:
StateTransitions: no transaction; current state
[jira] [Comment Edited] (JDO-767) JDO TCK lifecycle tests fail
[
https://issues.apache.org/jira/browse/JDO-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271531#comment-16271531
]
Michael Bouschen edited comment on JDO-767 at 11/29/17 9:01 PM:
I checked out a new workspace and switched to DN version 5.1.5-SNAPSHOT
(version Nov 29, 2017). I'm running the TCK on a mac, with mvn 3.3.9 and jdk
1.8.0_151.
I get the following test failures:
{noformat}
dsid-lifecycle-junit.txt:
** Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0
app-lifecycle-junit.txt:
** Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0
{noformat}
Details see below.
I also see the following exception in dsid-lifecycle-jdori.txt and
app-lifecycle-jdori.txt. I have no idea whether this is related to the test
failures:
{noformat}
ERROR [DataNucleus.MetaData] - Class
org.apache.jdo.tck.pc.compositeAnnotation.ApplicationIdDiscriminatorClassName
has application-identity and no objectid-class specified yet has 0 primary key
fields. Unable to use SingleFieldIdentity.
{noformat}
Here are the details of the test failures. They look the same as the ones Craig
desribes above:
{noformat}
1)
testDatastoreRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreRollback)junit.framework.AssertionFailedError:
Assertion A5.6.2-6 (NontransactionalWriteDatastoreRollback) failed: after
datastore rollback
expected: 100
actual: 999
2)
testDatastoreCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreCommitConflict)junit.framework.AssertionFailedError:
Assertion A5.6.2-4 (NontransactionalWriteDatastoreCommitConflict) failed: after
datastore commit with conflict
expected: 999
actual: 555
3)
testOptimisticRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticRollback)junit.framework.AssertionFailedError:
Assertion A5.6.2-10 (NontransactionalWriteOptimisticRollback) failed: after
optimistic rollback
expected: 100
actual: 999
4)
testOptimisticCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticCommitConflict)junit.framework.AssertionFailedError:
Assertion A5.6.2-8 (NontransactionalWriteOptimisticCommitConflict) failed:
after optimistic commit with conflicttransaction succeeded but should not
succeed.
5)
test(org.apache.jdo.tck.lifecycle.StateTransitions)junit.framework.AssertionFailedError:
Assertions A5.9-1 through A5.9-190 (StateTransitions) failed:
StateTransitions: no transaction; current state persistent-nontransactional
write field outside tx transitioned instance to invalid state hollow; expected
state persistent-nontransactional-dirty
{noformat}
was (Author: mbo):
I checked out a new workspace and switched to DN version 5.1.5-SNAPSHOT
(version Nov 29, 2017). I'm running the TCK on a mac, with mvn 3.3.9 and jdk
1.8.0_151.
I get the following test failures:
dsid-lifecycle-junit.txt: Tests run: 017, Time: 002 seconds. Failures: 5,
Errors: 0
app-lifecycle-junit.txt: Tests run: 017, Time: 002 seconds. Failures: 5,
Errors: 0
Details see below.
I also see the following exception in dsid-lifecycle-jdori.txt and
app-lifecycle-jdori.txt. I have no idea whether this is related to the test
failures:
ERROR [DataNucleus.MetaData] - Class
org.apache.jdo.tck.pc.compositeAnnotation.ApplicationIdDiscriminatorClassName
has application-identity and no objectid-class specified yet has 0 primary key
fields. Unable to use SingleFieldIdentity.
Here are the details of the test failures. They look the sasme as the ones
Craig desribes above:
1)
testDatastoreRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreRollback)junit.framework.AssertionFailedError:
Assertion A5.6.2-6 (NontransactionalWriteDatastoreRollback) failed: after
datastore rollback
expected: 100
actual: 999
2)
testDatastoreCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreCommitConflict)junit.framework.AssertionFailedError:
Assertion A5.6.2-4 (NontransactionalWriteDatastoreCommitConflict) failed: after
datastore commit with conflict
expected: 999
actual: 555
3)
testOptimisticRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticRollback)junit.framework.AssertionFailedError:
Assertion A5.6.2-10 (NontransactionalWriteOptimisticRollback) failed: after
optimistic rollback
expected: 100
actual: 999
4)
testOptimisticCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticCommitConflict)junit.framework.AssertionFailedError:
Assertion A5.6.2-8 (NontransactionalWriteOptimisticCommitConflict) failed:
after optimistic commit with conflicttransaction succeeded but should not
succeed.
5)
test(org.apache.jdo.tck.lifecycle.StateTransitions)junit.framework.AssertionFailedError:
Assertions A5.9-1 through A5.9-190 (StateTransitions) failed:
StateTransitions: no transaction; current state persistent-nontransactional
write field outside tx transitioned
[jira] [Comment Edited] (JDO-767) JDO TCK lifecycle tests fail
[ https://issues.apache.org/jira/browse/JDO-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271531#comment-16271531 ] Michael Bouschen edited comment on JDO-767 at 11/29/17 8:59 PM: I checked out a new workspace and switched to DN version 5.1.5-SNAPSHOT (version Nov 29, 2017). I'm running the TCK on a mac, with mvn 3.3.9 and jdk 1.8.0_151. I get the following test failures: dsid-lifecycle-junit.txt: Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0 app-lifecycle-junit.txt: Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0 Details see below. I also see the following exception in dsid-lifecycle-jdori.txt and app-lifecycle-jdori.txt. I have no idea whether this is related to the test failures: ERROR [DataNucleus.MetaData] - Class org.apache.jdo.tck.pc.compositeAnnotation.ApplicationIdDiscriminatorClassName has application-identity and no objectid-class specified yet has 0 primary key fields. Unable to use SingleFieldIdentity. Here are the details of the test failures. They look the sasme as the ones Craig desribes above: 1) testDatastoreRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreRollback)junit.framework.AssertionFailedError: Assertion A5.6.2-6 (NontransactionalWriteDatastoreRollback) failed: after datastore rollback expected: 100 actual: 999 2) testDatastoreCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreCommitConflict)junit.framework.AssertionFailedError: Assertion A5.6.2-4 (NontransactionalWriteDatastoreCommitConflict) failed: after datastore commit with conflict expected: 999 actual: 555 3) testOptimisticRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticRollback)junit.framework.AssertionFailedError: Assertion A5.6.2-10 (NontransactionalWriteOptimisticRollback) failed: after optimistic rollback expected: 100 actual: 999 4) testOptimisticCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticCommitConflict)junit.framework.AssertionFailedError: Assertion A5.6.2-8 (NontransactionalWriteOptimisticCommitConflict) failed: after optimistic commit with conflicttransaction succeeded but should not succeed. 5) test(org.apache.jdo.tck.lifecycle.StateTransitions)junit.framework.AssertionFailedError: Assertions A5.9-1 through A5.9-190 (StateTransitions) failed: StateTransitions: no transaction; current state persistent-nontransactional write field outside tx transitioned instance to invalid state hollow; expected state persistent-nontransactional-dirty was (Author: mbo): I checked out a new workspace and switched to DN version 5.1.5-SNAPSHOT (version Nov 29, 2017). I'm running the TCK on a mac, with mvn 3.3.9 and jdk 1.8.0_151. I get the following test failures: dsid-lifecycle-junit.txt: '** Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0 app-lifecycle-junit.txt: '** Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0 Details see below. I also see the following exception in dsid-lifecycle-jdori.txt and app-lifecycle-jdori.txt. I have no idea whether this is related to the test failures: ERROR [DataNucleus.MetaData] - Class org.apache.jdo.tck.pc.compositeAnnotation.ApplicationIdDiscriminatorClassName has application-identity and no objectid-class specified yet has 0 primary key fields. Unable to use SingleFieldIdentity. Here are the details of the test failures. They look the sasme as the ones Craig desribes above: 1) testDatastoreRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreRollback)junit.framework.AssertionFailedError: Assertion A5.6.2-6 (NontransactionalWriteDatastoreRollback) failed: after datastore rollback expected: 100 actual: 999 2) testDatastoreCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreCommitConflict)junit.framework.AssertionFailedError: Assertion A5.6.2-4 (NontransactionalWriteDatastoreCommitConflict) failed: after datastore commit with conflict expected: 999 actual: 555 3) testOptimisticRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticRollback)junit.framework.AssertionFailedError: Assertion A5.6.2-10 (NontransactionalWriteOptimisticRollback) failed: after optimistic rollback expected: 100 actual: 999 4) testOptimisticCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticCommitConflict)junit.framework.AssertionFailedError: Assertion A5.6.2-8 (NontransactionalWriteOptimisticCommitConflict) failed: after optimistic commit with conflicttransaction succeeded but should not succeed. 5) test(org.apache.jdo.tck.lifecycle.StateTransitions)junit.framework.AssertionFailedError: Assertions A5.9-1 through A5.9-190 (StateTransitions) failed: StateTransitions: no transaction; current state persistent-nontransactional write field outside tx transitioned instance to invalid state hollow; expected state
[jira] [Comment Edited] (JDO-767) JDO TCK lifecycle tests fail
[ https://issues.apache.org/jira/browse/JDO-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271531#comment-16271531 ] Michael Bouschen edited comment on JDO-767 at 11/29/17 8:59 PM: I checked out a new workspace and switched to DN version 5.1.5-SNAPSHOT (version Nov 29, 2017). I'm running the TCK on a mac, with mvn 3.3.9 and jdk 1.8.0_151. I get the following test failures: dsid-lifecycle-junit.txt: '** Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0 app-lifecycle-junit.txt: '** Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0 Details see below. I also see the following exception in dsid-lifecycle-jdori.txt and app-lifecycle-jdori.txt. I have no idea whether this is related to the test failures: ERROR [DataNucleus.MetaData] - Class org.apache.jdo.tck.pc.compositeAnnotation.ApplicationIdDiscriminatorClassName has application-identity and no objectid-class specified yet has 0 primary key fields. Unable to use SingleFieldIdentity. Here are the details of the test failures. They look the sasme as the ones Craig desribes above: 1) testDatastoreRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreRollback)junit.framework.AssertionFailedError: Assertion A5.6.2-6 (NontransactionalWriteDatastoreRollback) failed: after datastore rollback expected: 100 actual: 999 2) testDatastoreCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreCommitConflict)junit.framework.AssertionFailedError: Assertion A5.6.2-4 (NontransactionalWriteDatastoreCommitConflict) failed: after datastore commit with conflict expected: 999 actual: 555 3) testOptimisticRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticRollback)junit.framework.AssertionFailedError: Assertion A5.6.2-10 (NontransactionalWriteOptimisticRollback) failed: after optimistic rollback expected: 100 actual: 999 4) testOptimisticCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticCommitConflict)junit.framework.AssertionFailedError: Assertion A5.6.2-8 (NontransactionalWriteOptimisticCommitConflict) failed: after optimistic commit with conflicttransaction succeeded but should not succeed. 5) test(org.apache.jdo.tck.lifecycle.StateTransitions)junit.framework.AssertionFailedError: Assertions A5.9-1 through A5.9-190 (StateTransitions) failed: StateTransitions: no transaction; current state persistent-nontransactional write field outside tx transitioned instance to invalid state hollow; expected state persistent-nontransactional-dirty was (Author: mbo): I checked out a new workspace and switched to DN version 5.1.5-SNAPSHOT (version Nov 29, 2017). I'm running the TCK on a mac, with mvn 3.3.9 and jdk 1.8.0_151. I get the following test failures: dsid-lifecycle-junit.txt: ** Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0 app-lifecycle-junit.txt: ** Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0 Details see below. I also see the following exception in dsid-lifecycle-jdori.txt and app-lifecycle-jdori.txt. I have no idea whether this is related to the test failures: ERROR [DataNucleus.MetaData] - Class org.apache.jdo.tck.pc.compositeAnnotation.ApplicationIdDiscriminatorClassName has application-identity and no objectid-class specified yet has 0 primary key fields. Unable to use SingleFieldIdentity. Here are the details of the test failures. They look the sasme as the ones Craig desribes above: 1) testDatastoreRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreRollback)junit.framework.AssertionFailedError: Assertion A5.6.2-6 (NontransactionalWriteDatastoreRollback) failed: after datastore rollback expected: 100 actual: 999 2) testDatastoreCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreCommitConflict)junit.framework.AssertionFailedError: Assertion A5.6.2-4 (NontransactionalWriteDatastoreCommitConflict) failed: after datastore commit with conflict expected: 999 actual: 555 3) testOptimisticRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticRollback)junit.framework.AssertionFailedError: Assertion A5.6.2-10 (NontransactionalWriteOptimisticRollback) failed: after optimistic rollback expected: 100 actual: 999 4) testOptimisticCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticCommitConflict)junit.framework.AssertionFailedError: Assertion A5.6.2-8 (NontransactionalWriteOptimisticCommitConflict) failed: after optimistic commit with conflicttransaction succeeded but should not succeed. 5) test(org.apache.jdo.tck.lifecycle.StateTransitions)junit.framework.AssertionFailedError: Assertions A5.9-1 through A5.9-190 (StateTransitions) failed: StateTransitions: no transaction; current state persistent-nontransactional write field outside tx transitioned instance to invalid state hollow; expected state
[jira] [Comment Edited] (JDO-767) JDO TCK lifecycle tests fail
[ https://issues.apache.org/jira/browse/JDO-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271531#comment-16271531 ] Michael Bouschen edited comment on JDO-767 at 11/29/17 8:58 PM: I checked out a new workspace and switched to DN version 5.1.5-SNAPSHOT (version Nov 29, 2017). I'm running the TCK on a mac, with mvn 3.3.9 and jdk 1.8.0_151. I get the following test failures: dsid-lifecycle-junit.txt: ** Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0 app-lifecycle-junit.txt: ** Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0 Details see below. I also see the following exception in dsid-lifecycle-jdori.txt and app-lifecycle-jdori.txt. I have no idea whether this is related to the test failures: ERROR [DataNucleus.MetaData] - Class org.apache.jdo.tck.pc.compositeAnnotation.ApplicationIdDiscriminatorClassName has application-identity and no objectid-class specified yet has 0 primary key fields. Unable to use SingleFieldIdentity. Here are the details of the test failures. They look the sasme as the ones Craig desribes above: 1) testDatastoreRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreRollback)junit.framework.AssertionFailedError: Assertion A5.6.2-6 (NontransactionalWriteDatastoreRollback) failed: after datastore rollback expected: 100 actual: 999 2) testDatastoreCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreCommitConflict)junit.framework.AssertionFailedError: Assertion A5.6.2-4 (NontransactionalWriteDatastoreCommitConflict) failed: after datastore commit with conflict expected: 999 actual: 555 3) testOptimisticRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticRollback)junit.framework.AssertionFailedError: Assertion A5.6.2-10 (NontransactionalWriteOptimisticRollback) failed: after optimistic rollback expected: 100 actual: 999 4) testOptimisticCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticCommitConflict)junit.framework.AssertionFailedError: Assertion A5.6.2-8 (NontransactionalWriteOptimisticCommitConflict) failed: after optimistic commit with conflicttransaction succeeded but should not succeed. 5) test(org.apache.jdo.tck.lifecycle.StateTransitions)junit.framework.AssertionFailedError: Assertions A5.9-1 through A5.9-190 (StateTransitions) failed: StateTransitions: no transaction; current state persistent-nontransactional write field outside tx transitioned instance to invalid state hollow; expected state persistent-nontransactional-dirty was (Author: mbo): I checked out a new workspace and switched to DN version 5.1.5-SNAPSHOT (version Nov 29, 2017). I'm running the TCK on a mac, with mvn 3.3.9 and jdk 1.8.0_151. I get the following test failures: - dsid-lifecycle-junit.txt: ** Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0 - app-lifecycle-junit.txt: ** Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0 Details see below. I also see the following exception in dsid-lifecycle-jdori.txt and app-lifecycle-jdori.txt. I have no idea whether this is related to the test failures: ERROR [DataNucleus.MetaData] - Class org.apache.jdo.tck.pc.compositeAnnotation.ApplicationIdDiscriminatorClassName has application-identity and no objectid-class specified yet has 0 primary key fields. Unable to use SingleFieldIdentity. Here are the details of the test failures. They look the sasme as the ones Craig desribes above: 1) testDatastoreRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreRollback)junit.framework.AssertionFailedError: Assertion A5.6.2-6 (NontransactionalWriteDatastoreRollback) failed: after datastore rollback expected: 100 actual: 999 2) testDatastoreCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreCommitConflict)junit.framework.AssertionFailedError: Assertion A5.6.2-4 (NontransactionalWriteDatastoreCommitConflict) failed: after datastore commit with conflict expected: 999 actual: 555 3) testOptimisticRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticRollback)junit.framework.AssertionFailedError: Assertion A5.6.2-10 (NontransactionalWriteOptimisticRollback) failed: after optimistic rollback expected: 100 actual: 999 4) testOptimisticCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticCommitConflict)junit.framework.AssertionFailedError: Assertion A5.6.2-8 (NontransactionalWriteOptimisticCommitConflict) failed: after optimistic commit with conflicttransaction succeeded but should not succeed. 5) test(org.apache.jdo.tck.lifecycle.StateTransitions)junit.framework.AssertionFailedError: Assertions A5.9-1 through A5.9-190 (StateTransitions) failed: StateTransitions: no transaction; current state persistent-nontransactional write field outside tx transitioned instance to invalid state hollow; expected state
[jira] [Commented] (JDO-767) JDO TCK lifecycle tests fail
[ https://issues.apache.org/jira/browse/JDO-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271531#comment-16271531 ] Michael Bouschen commented on JDO-767: -- I checked out a new workspace and switched to DN version 5.1.5-SNAPSHOT (version Nov 29, 2017). I'm running the TCK on a mac, with mvn 3.3.9 and jdk 1.8.0_151. I get the following test failures: - dsid-lifecycle-junit.txt: ** Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0 - app-lifecycle-junit.txt: ** Tests run: 017, Time: 002 seconds. Failures: 5, Errors: 0 Details see below. I also see the following exception in dsid-lifecycle-jdori.txt and app-lifecycle-jdori.txt. I have no idea whether this is related to the test failures: ERROR [DataNucleus.MetaData] - Class org.apache.jdo.tck.pc.compositeAnnotation.ApplicationIdDiscriminatorClassName has application-identity and no objectid-class specified yet has 0 primary key fields. Unable to use SingleFieldIdentity. Here are the details of the test failures. They look the sasme as the ones Craig desribes above: 1) testDatastoreRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreRollback)junit.framework.AssertionFailedError: Assertion A5.6.2-6 (NontransactionalWriteDatastoreRollback) failed: after datastore rollback expected: 100 actual: 999 2) testDatastoreCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreCommitConflict)junit.framework.AssertionFailedError: Assertion A5.6.2-4 (NontransactionalWriteDatastoreCommitConflict) failed: after datastore commit with conflict expected: 999 actual: 555 3) testOptimisticRollback(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticRollback)junit.framework.AssertionFailedError: Assertion A5.6.2-10 (NontransactionalWriteOptimisticRollback) failed: after optimistic rollback expected: 100 actual: 999 4) testOptimisticCommitConflict(org.apache.jdo.tck.lifecycle.NontransactionalWriteOptimisticCommitConflict)junit.framework.AssertionFailedError: Assertion A5.6.2-8 (NontransactionalWriteOptimisticCommitConflict) failed: after optimistic commit with conflicttransaction succeeded but should not succeed. 5) test(org.apache.jdo.tck.lifecycle.StateTransitions)junit.framework.AssertionFailedError: Assertions A5.9-1 through A5.9-190 (StateTransitions) failed: StateTransitions: no transaction; current state persistent-nontransactional write field outside tx transitioned instance to invalid state hollow; expected state persistent-nontransactional-dirty > JDO TCK lifecycle tests fail > > > Key: JDO-767 > URL: https://issues.apache.org/jira/browse/JDO-767 > Project: JDO > Issue Type: Bug > Components: tck >Affects Versions: JDO 3.1 >Reporter: Craig L Russell >Assignee: Tilmann Zäschke > Fix For: JDO 3.2 > > > cat dsid-lifecycle-tck.txt > 10:14:11,507 (main) INFO [org.apache.jdo.tck] - Exception during setUp or > runtest: > junit.framework.AssertionFailedError: > Assertion A5.6.2-6 (NontransactionalWriteDatastoreRollback) failed: after > datastore rollback > expected: 100 > actual: 999 > at junit.framework.Assert.fail(Assert.java:47) > at org.apache.jdo.tck.JDO_Test.failOnError(JDO_Test.java:1245) > at > org.apache.jdo.tck.lifecycle.NontransactionalWriteDatastoreRollback.testDatastoreRollback(NontransactionalWriteDatastoreRollback.java:87) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at junit.framework.TestCase.runTest(TestCase.java:154) > at org.apache.jdo.tck.JDO_Test.runBare(JDO_Test.java:284) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at junit.textui.TestRunner.doRun(TestRunner.java:116) > at > org.apache.jdo.tck.util.BatchTestRunner.doRun(BatchTestRunner.java:108) > at > org.apache.jdo.tck.util.BatchTestRunner.start(BatchTestRunner.java:148) > at > org.apache.jdo.tck.util.BatchTestRunner.main(BatchTestRunner.java:123) > 10:14:11,527 (main) INFO [org.apache.jdo.tck] - Exception during setUp or > runtest: > junit.framework.AssertionFailedError: > Assertion A5.6.2-4
[jira] [Comment Edited] (JDO-768) Failure in api test case testGetPMFNullResource(javax.jdo.JDOHelperTest)
[
https://issues.apache.org/jira/browse/JDO-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266171#comment-16266171
]
Michael Bouschen edited comment on JDO-768 at 11/29/17 8:37 PM:
It turns out the test PMFMapMapTest is causing the problem. A number of test
methods set the context class loader to a specific resouce class loader without
resetting the context class loader at the end of the test. So this context
class loader is able to find the specified resource, where the default context
class loader does not. The attached path JDO-768-patch.txt changes class
PMFMapMapTest to reset the context class loader.
was (Author: mbo):
It truns out the test PMFMapMapTest is causing the problem. A number of test
methods set the context class loader to a specific resouce class loader without
resetting the context class loader at the end of the test. So this context
class loader is able to find the specified resource, where the default context
class loader does not. The attached path JDO-768-patch.txt changes class
PMFMapMapTest to reset the context class loader.
> Failure in api test case testGetPMFNullResource(javax.jdo.JDOHelperTest)
> -
>
> Key: JDO-768
> URL: https://issues.apache.org/jira/browse/JDO-768
> Project: JDO
> Issue Type: Bug
> Components: api
>Affects Versions: JDO 3.1
>Reporter: Michael Bouschen
>Assignee: Michael Bouschen
>Priority: Critical
> Fix For: JDO 3.2
>
> Attachments: JDO-768-patch.txt
>
>
> Test method testGetPMFNullResource of API test class JDOHelperTest fails when
> running 'mvn clean verify' in the submodule api:
> {noformat}
> testGetPMFNullResource(javax.jdo.JDOHelperTest) Time elapsed: 0.003 sec <<<
> FAILURE!
> junit.framework.AssertionFailedError: Null resource name should result in
> JDOFatalUserException
> at junit.framework.Assert.fail(Assert.java:47)
> at
> javax.jdo.JDOHelperTest.testGetPMFNullResource(JDOHelperTest.java:196)
> {noformat}
> Please note, the test case succeeds when running it alone:
> {noformat}
> mvn -Dtest=javax.jdo.JDOHelperTest clean verify
> {noformat}
> It fails if the test case PMFMapMapTest is executed before JDOHelperTest:
> {noformat}
> mvn -Dtest=javax.jdo.PMFMapMapTest,javax.jdo.JDOHelperTest clean verify
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
