The GitHub Actions job "CI" on grails-core.git/fix/neo4j-ci-flakes has succeeded. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: d03fbba01b98efabba778e9aca87c025032344cd / James Daugherty <[email protected]> Fix the two intermittent Neo4j functional test failures The Neo4j CI jobs failed on random JDKs of the matrix for two unrelated reasons, found by surveying every gradle.yml run since 2026-09-16: 1. Dependency resolution died on repo.grails.org ("Remote host terminated the handshake") before any test ran. GrailsRepoSettingsPlugin declared repo.grails.org/grails/restricted as the only release repository, and Gradle never falls through to another repository on a transport failure. The jobs using setup-gradle's basic cache provider all shared one ~300 MB entry written by the fast validate job, so every Neo4j run re-downloaded the GORM dependency set through that host. 2. MultiTenancySpec and HasManyInheritanceSpec both started an embedded Neo4j on the pinned port 7687. grails-data-neo4j-core runs its tests across parallel forks, so whenever the two specs ran concurrently the second one failed with PortBindException. Maven Central is now the first release repository, with repo.grails.org kept as the fallback for anything Central does not host; a TestKit spec pins the repository order. The eight basic-provider CI jobs use the same branch-keyed dependency jar cache as the other jobs instead of per-job entries, because the repository is already at its 10 GB cache limit and every test family needs roughly the same ~1 GB working set. The two specs drop the pinned URL so the embedded server binds a random free port like the TCK manager already does. Report URL: https://github.com/apache/grails-core/actions/runs/36736284183 With regards, GitHub Actions via GitBox
