The GitHub Actions job "CI" on grails-core.git/feat/gorm-lock-latest has failed. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: 5ce12a7a99f290870f96dc3264c638f40ec4d841 / James Daugherty <[email protected]> test: cover named-connection instance operations on MongoDB The qualifier routing change is in shared code, so it reaches every datastore, and review asked whether MongoDB breaks under it. Nothing covered the changed surface there: the existing multiple connections spec drives withConnection and a plain instance save, not the instance operations that hang off a named-connection static handle. MultipleConnectionsSpec now saves and deletes through CompanyA.test2 itself and asserts the write lands on that connection and not on the entity's own default one, alongside a second feature pinning that an ordinary save still goes to the entity's first mapped connection. Measured on this branch with GormStaticApi.save(D, Map) restored to its previous null, the new named-connection feature fails - the write goes to the default connection while the handle correctly reports test2Db - and passes with the qualifier in place. So the change fixes the same defect on MongoDB that it fixes on Hibernate, rather than moving anything; the default-route feature passes either way. Neo4j has no equivalent coverage to extend: its own MultipleConnectionsSpec is disabled upstream because the bolt driver can no longer build a driver against a server that is down, and a real named-connection test there needs two embedded harness servers. The full suite is green. Suites: grails-data-mongodb-core 736 tests, 45 skipped; grails-data-neo4j-core 582 tests, 99 skipped; no failures. codeStyle clean. Report URL: https://github.com/apache/grails-core/actions/runs/35608631115 With regards, GitHub Actions via GitBox
