[
https://issues.apache.org/jira/browse/DERBY-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741433#action_12741433
]
Kathey Marsden commented on DERBY-4344:
---------------------------------------
Myrna analyzed the issues and determined
- The windows run failed to start due to a configuration issue.
- The linux run coincided with some vmware changes which in addition to
introducing another variable seemed to cause our vm's to get reverted. Only
1.4.2. started and hung but many tests failed before this occurred, mostly
related to network server bind errors. We also had a strange failure I have
never seen before:
*** Start: TestDurabilityProperty jdk1.4.2 storeall:storemore 2009-08-08
23:00:19 ***
1a2,5
> FAIL -- derby.system.durability=test mode seems to be broken.
> -- In this mode one would expect that inserts with autocommit off and on
> would be in the same range as syncs are not happening but the difference here
> seems to be more than the approximate estimated range.
> -- Also comparing the time taken to do the inserts without this property set
> seems to be in the same range as with this property set.
> -- Please note this test times inserts and approximate estimates were
> considered to report this observation.
Test Failed.
Myrna and I are starting manual runs now on both Windows and Linux with the
right vms and without vmware. Prior to my checkin I ran suites.All and
derbyall on IBM 1.6 on Windows XP and it ran fine.
> Track changes needed for 10.5.3 release
> ---------------------------------------
>
> Key: DERBY-4344
> URL: https://issues.apache.org/jira/browse/DERBY-4344
> Project: Derby
> Issue Type: Task
> Components: Build tools
> Affects Versions: 10.5.3.0
> Reporter: Rick Hillegas
>
> Issue to track release activity for 10.5.3.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
