The GitHub Actions job "Coverage" on grails-core.git/test/h7-functional-coverage has failed. Run started by GitHub user jamesfredley (triggered by jamesfredley).
Head commit for run: 08ae34fa368637cc9fa320bf96730c27cbb9f464 / James Fredley <[email protected]> Extend bidirectional H5/H7 test parity with documented version differences Adds the remaining genuinely-shared behavioral specs to the side that was missing them, and locks the real Hibernate 5 vs Hibernate 7 behavior differences with per-side assertions (verified by running on both lines): Hibernate 5 (ported from Hibernate 7, all pass on H5): - grails/gorm/tests/AddToManagedEntitySpec - addTo*/save on a managed entity. - org/grails/datastore/gorm/GormEnhancerCleanupSpec - GormEnhancer.DATASTORES registry cleanup on datastore.close(). - org/grails/datastore/mapping/model/PersistentPropertySpec - isUnidirectional OneToMany is identical; the isLazyAble feature documents that a unidirectional one-to-many is not lazy-able in Hibernate 5 (Hibernate 7 reports it lazy-able). - grails/gorm/tests/NullValueEqualSpec - the not-equal feature documents that Hibernate 5 follows SQL three-valued logic (countByAgeNotEqual(11) == 0, excluding null-aged rows) where Hibernate 7 includes null-valued rows (== 2). The shared TCK NullValueEqualSpec skips this feature under the gorm.suite system property, so each module needs its own local coverage. Hibernate 7 (reverse gap - ported from Hibernate 5, all pass on H7): - grails/gorm/tests/proxy/ByteBuddyProxySpec - default ByteBuddy proxy getId/id /truthy/association checks do not initialize the proxy. The isDirty feature documents that Hibernate 7 does not initialize the proxy on a clean isDirty() check (Hibernate 5 does). Assisted-by: claude-code:claude-4.8-opus Report URL: https://github.com/apache/grails-core/actions/runs/27657063532 With regards, GitHub Actions via GitBox
