The GitHub Actions job "CI" on grails-core.git/feat/neo4j-gorm-registry-migration has succeeded. Run started by GitHub user borinquenkid (triggered by borinquenkid).
Head commit for run: 37c67e5950766659bceb4d696292d68d51f89b98 / Walter Duque de Estrada <[email protected]> test(tck): skip TCK criteria-pagination-without-sort feature for Neo4j Fixing the two TCK gaps under grails-data-neo4j-core:test (this module only started running the shared TCK suite when this PR folded the standalone Neo4j build into the root settings.gradle) surfaced a second one: OptimisticLockingSpec's fix landed separately, this covers PagedResultSpec. "Test that a paged result list is returned from the critera with pagination params" asserts a specific row order from Person.createCriteria().list(offset:1, max:2) { ... } with no explicit sort. Neo4j's criteria query has no implicit ORDER BY, so an unordered page is not guaranteed to come back in insertion order - unlike list(), whose equivalent unsorted-pagination feature passes reliably. Neo4j's own adapted copy of this exact test (grails.gorm.tests.PagedResultSpec in grails-data-neo4j-core) already covers the same scenario with an explicit sort added, with a historical comment noting it was "temporarily disabled due to undefined sorting order" before that fix - direct precedent that this is a known, structural ordering gap rather than new flakiness. Only the criteria-based feature is skipped; the list()-based unsorted pagination feature is left alone since it has no observed failure. Verified: grails-data-neo4j-core:test green 3/3 --rerun-tasks runs (BUILD SUCCESSFUL); TCK report shows skipped=1, 0 failures across all 6 TCK features; Neo4j's own adapted PagedResultSpec still runs both of its features unskipped, 0 failures. Co-Authored-By: Claude Sonnet 5 <[email protected]> Report URL: https://github.com/apache/grails-core/actions/runs/30710719961 With regards, GitHub Actions via GitBox
