Re: JDO-61

Mystery solved, I think.The JPOX log shows that the test that fails doesn't select for part time employees, so it misses one of the rows in the database. The test that succeeds selects for Employee, PartTimeEmployee, and FullTimeEmployee.I don't know the solution, just the symptom.Here's the JPOX l

Re: JDO-61

Yes, I would assume that it is a clean-up issue. In fact, I ran a different test immediately after this one (CompletenessTest) and got a duplicate key error that I don't get when I run the CompletenessTest on its own, so it must be leaving some company model object in the database. -- Michell

Re: JDO-61

Hi Michelle, I think this is a database init/cleanup issue. The tests are cleverly written to do a very simple test to see if the database is initialized, and the test isn't reliable. But the fact that the same test run twice fails means that either the test is doing something wrong or th

JDO TCK Conference Call Friday, Jun 10, 9 am PST

Hi, We will have our regular meeting Friday, June 10 at 9 am PST to discuss JDO TCK issues and status. Dial-in numbers are: 866 230-6968 294-0479# International: +1 865 544-7856 Agenda: Test status (Craig, Michelle) TestRunner status(Michelle) Double-check locking in the PMF (Martin) Det

Re: JDO-61

Yup, it passes on the first run with a clean database, but if you run the same test a second time it fails. I've added a comment to the JIRA. -- Michelle Andy Jefferson wrote: Is there anything in cvs but not in the latest build that would cause this test to pass? Are you running with the s

Re: JDO-61

> Is there anything in cvs but not in the latest build that would cause > this test to pass? > > Are you running with the same jdo properties that we do (checked into > test/conf)? What I use is :- Apache JDO : SVN JPOX : CVS I changed a few things in extent handling this morning but nothing of

Patch for JIRA JDO-33

Hi, JIRA JDO-33 suggests to print the TCK output to a log file in addition to standard out. The attached patch solves this issue. The log file is created in directory "target/logs". If this directory does not exist at the time the TCK is started, then it is created. The file name pattern for

Re: JDO-61

Hi Andy, I downloaded the latest JPOX nightly build and I still get the error reported in JDO-61. Is there anything in cvs but not in the latest build that would cause this test to pass? Are you running with the same jdo properties that we do (checked into test/conf)? javax.jdo.Persisten

Re: Multithreaded query test fails

Hi Craig, I can reproduce the exception. The exception is thrown because the call "super.executeQueries(pm)" in method "ExecutingMultipleQueriesSimultaneouslyIsThreadSafe.executeQueries(PersistenceManager" is not executed inside a transaction. If you add begin/commit the test succeeds. How

Re: JDO-61

> After I fixed the extent iteration outside a transaction, it appears > that JPOX fails test InstancesPersistedPriorToIterationReturned > because it doesn't include a new instance in the iteration. > > Could you please look at JDO-61? Hi Craig, I ran that test on its own - for both datastore ide