[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5222) upgrade from READ to OPTIMISTIC_FORCE_INCREMENT fails

[Scott Marlow (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44430#comment-44430 ] 

Scott Marlow commented on HHH-5222:
-----------------------------------

Strong, what does the above error have to do with the HHH-5222 change?  

I agree that we should fix the other failures, like but
https://ci.jboss.org/hudson/job/hibernate-core-master-matrix/117/database=oracle11gR1RAC,jdk=java16_default,label=hibernate/testReport/junit/org.hibernate.ejb.test.lock/LockTest/testContendedPessimisticReadLockTimeout/

But, the upgrade test appears to be passing:
https://ci.jboss.org/hudson/job/hibernate-core-master-matrix/117/database=oracle11gR2RAC,jdk=java16_default,label=hibernate/testReport/org.hibernate.ejb.test.lock/UpgradeLockTest/

Also, the mysql test didn't have failures.  

The Oracle failures should be reported with a new jira, I think. 

I'll close this jira and if you agree, can you create a new jira for the failures that you are concerned with.

> upgrade from READ to OPTIMISTIC_FORCE_INCREMENT fails
> -----------------------------------------------------
>
>                 Key: HHH-5222
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5222
>             Project: Hibernate Core
>          Issue Type: Bug
>    Affects Versions: 3.6.8, 4.0.0.CR6
>            Reporter: Scott Marlow
>            Assignee: Scott Marlow
>             Fix For: 4.0.0.next
>
>         Attachments: HHH-5222-test.txt
>
>
> See hhh5032-2.patch attached to HHH-5032 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira