You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@grails.apache.org by "codeconsole (via GitHub)" <gi...@apache.org> on 2026/08/18 23:16:19 UTC

[PR] feat: publish Groovy artifacts with and without invokedynamic [grails-core]

codeconsole opened a new pull request, #16170:
URL: https://github.com/apache/grails-core/pull/16170

   Groovy compiles dynamic dispatch either as `invokedynamic` or as call-site caching bytecode. Which is faster depends on the application, but the choice was previously fixed at compile time and could not reach the framework and plugin jars an application already depends on.
   
   This publishes every Groovy module and Grails plugin twice: a default artifact using Groovy's own `invokedynamic` default, and a `noindy` classifier artifact compiled without it. An application sets `grails.indy` and the choice propagates across the whole dependency graph.
   
   ### Why not the classifier alone
   
   A Maven classifier artifact shares the POM of the main artifact, so asking for one by classifier pulls the *default* flavour of everything it depends on — one noindy jar in a graph of indy jars. The noindy artifact is instead published as a **secondary variant** of `apiElements`/`runtimeElements`, which inherits their dependencies, so a single request applies transitively. The classifier remains how the artifact is packaged, not how it is selected.
   
   ### Only the noindy variants declare the attribute
   
   The default variants deliberately leave `org.apache.grails.indy` unset. A consumer that never requests it — any plain Gradle project not applying a Grails plugin — sees one candidate and resolves the default artifact exactly as before. Declaring it on both variants makes every such build fail with `There are several available matching variants`, which an earlier revision of this branch did.
   
   A dependency publishing a single artifact (a plugin built before this, or one opting out) stays resolvable under either setting, since the two flavours interoperate on the same classpath.
   
   ### Default now follows Groovy
   
   `grails.indy` defaulted to `false`; it now defaults to `true`. Native compilation is the reason: call-site caching bytecode links call sites at runtime and cannot be compiled ahead of time, so every artifact on a native application's classpath must be the `invokedynamic` flavour. `indy = false` is an opt-out that forfeits native compilation.
   
   This also resolves an existing incoherence — the framework currently ships mixed bytecode (`grails-controllers` indy-on, `grails-gsp` indy-off) purely from which modules happened to adopt `grails-plugin`.
   
   `grails.indy` no longer governs how a plugin compiles its own sources, since a plugin builds both flavours and the resolving application chooses.
   
   ### Tests
   
   8 functional tests in `GrailsIndyVariantsSpec` covering: both flavours compiled and byte-different, variants published on both element configurations, application selection, fallback for single-artifact dependencies, the new default, and that a plain Gradle consumer is unaffected.
   
   Verified on a real framework module: `AllowedMethodsHelper.class` carries 2 `invokedynamic` instructions in the default jar and 0 in the noindy jar. `grails-cache`, where both producer paths can reach the same project, builds one `noindyJar` without collision.
   
   ### Reviewer notes
   
   - Full `./gradlew build` has not been run — 2 of ~137 modules were built locally.
   - The cost is real: Groovy compilation roughly doubles, as does the artifact count per release (signing, SBOM, vulnerability scan).
   - Given the native constraint, an alternative worth weighing is dropping dual publication entirely and making `indy` an application-only option so every published artifact is `invokedynamic`. A companion PR follows with that approach.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@grails.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat: publish Groovy artifacts with and without invokedynamic [grails-core]

Posted by "testlens-app[bot] (via GitHub)" <gi...@apache.org>.
testlens-app[bot] commented on PR #16170:
URL: https://github.com/apache/grails-core/pull/16170#issuecomment-5335581493

   ## ✅ All tests passed ✅
   
   🏷️ Commit: 40008be7322aa2e17cf7403a67b9a512a4ac2418
   ▶️ Tests:  472 executed
   ⚪️ Checks: 77/77 completed
   
   ---
   _Learn more about TestLens at [testlens.app](https://testlens.app)._
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@grails.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat!: make callsite caching the default and publish invokedynamic under a classifier [grails-core]

Posted by "jamesfredley (via GitHub)" <gi...@apache.org>.
jamesfredley commented on PR #16170:
URL: https://github.com/apache/grails-core/pull/16170#issuecomment-5356850931

   @codeconsole https://github.com/apache/grails-core/pull/16178 and this PR have a lot of overlap for Grails 8 on Groovy 5.  Since Groovy 5 Indy is not fast enough in Grails I am not sure we need to publish the extra modules.
   
   Then on Groovy 6, we will flip everything to Indy, which will be the first time Grails is on Indy, with the exception of the narrow window at the beginning of Grails 7.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@grails.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat: publish Groovy artifacts with and without invokedynamic [grails-core]

Posted by "codeconsole (via GitHub)" <gi...@apache.org>.
codeconsole commented on PR #16170:
URL: https://github.com/apache/grails-core/pull/16170#issuecomment-5336663122

   Rebuilt on a different mechanism after CI failed. The original approach was not fixable.
   
   ### Why it failed
   
   Publishing the `noindy` jar as a secondary variant of `apiElements`/`runtimeElements` made every module ambiguous to a configuration that requests **no attributes at all**:
   
   ```
   Could not resolve all dependencies for configuration ':grails-data-hibernate5-core:tck'.
      > More than one variant of project ':grails-datamapping-tck' matches the consumer attributes:
          - Configuration ':grails-datamapping-tck:runtimeElements':
          - Configuration ':grails-datamapping-tck:runtimeElements' variant noindy:
   ```
   
   Every unmatched line reads *"but the consumer didn't ask for it"*, including `org.gradle.usage`. The `tck` and CLI companion probe configurations declare nothing, so every variant is an equally good candidate.
   
   No attribute rule repairs this. A disambiguation rule receives only the values candidates declare, so the variant *without* the attribute never appears among them — instrumenting the rule prints `RULE_INVOKED consumer=null candidates=[false]`, leaving no value meaning "the default one". Declaring the attribute on both variants makes the rule work but breaks every plain consumer of a Grails artifact, which is the problem that led to the asymmetry in the first place.
   
   Worth noting the one existing precedent here, `GrailsExplodedPlugin`, creates its secondary variant only `if (grails.developmentRun)` — it exists during `bootRun` and never during normal resolution, sidestepping the general case rather than solving it.
   
   ### What replaces it
   
   The `noindy` jar is now a plain Maven classifier that adds **nothing** to the published metadata — the module keeps exactly the variants it always had, so no consumer's resolution changes and the ambiguity is unreachable rather than fixed.
   
   Selection is assembled on the consuming side. An application setting `indy = false` registers a `ComponentMetadataRule` that derives a variant from the classifier for the modules it names:
   
   ```groovy
   grails {
       indy = false
       noindyModules = ['org.apache.grails:grails-core', 'com.example:my-plugin']
   }
   ```
   
   That variant exists only inside the opted-in build, whose schema also carries the disambiguation rule needed to choose between it and the main artifact.
   
   Verified across five scenarios, including the two that broke CI: an artifact view constraining nothing, and an ad-hoc configuration with no attributes. Both now resolve a single artifact. A dependency publishing only the main artifact still resolves under either setting.
   
   ### Two limitations, both inherent
   
   - **The module list is required.** Applying the rule unguarded fails hard — it tries to fetch `groovy-5.0.8-noindy.jar`. Platforms fail the same way, and the Grails BOM is a platform every app depends on, so there is no safe group-wide default. Modules advertise their classifier through a `Grails-Noindy-Artifact` manifest attribute (mirroring `Grails-Cli-Artifact`) so the list can later be discovered by a probe rather than written by hand; that discovery is not implemented.
   - **Component metadata rules do not apply to project dependencies**, so a composite or multi-project build always resolves the main artifact. Documented in the guide.
   
   ### Standing recommendation unchanged
   
   This makes the approach viable, not necessarily right. `noindy` artifacts still cannot appear in a native image, which was the motivation, and #16171 delivers the same native guarantee in 73 lines with no module list to maintain and green CI. I would still merge #16171 — but the choice is now a real trade-off rather than one option being unworkable.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@grails.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat: publish Groovy artifacts with and without invokedynamic [grails-core]

Posted by "codecov[bot] (via GitHub)" <gi...@apache.org>.
codecov[bot] commented on PR #16170:
URL: https://github.com/apache/grails-core/pull/16170#issuecomment-5335429030

   ## [Codecov](https://app.codecov.io/gh/apache/grails-core/pull/16170?dropdown=coverage&src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) Report
   :x: Patch coverage is `1.63934%` with `60 lines` in your changes missing coverage. Please review.
   :white_check_mark: Project coverage is 21.7155%. Comparing base ([`deac428`](https://app.codecov.io/gh/apache/grails-core/commit/deac428c1e74577bc6255a5cfc3ed4b9d9da4646?dropdown=coverage&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)) to head ([`40008be`](https://app.codecov.io/gh/apache/grails-core/commit/40008be7322aa2e17cf7403a67b9a512a4ac2418?dropdown=coverage&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)).
   
   | [Files with missing lines](https://app.codecov.io/gh/apache/grails-core/pull/16170?dropdown=coverage&src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | Patch % | Lines |
   |---|---|---|
   | [...rails/gradle/plugin/core/GrailsIndyVariants.groovy](https://app.codecov.io/gh/apache/grails-core/pull/16170?src=pr&el=tree&filepath=grails-gradle%2Fplugins%2Fsrc%2Fmain%2Fgroovy%2Forg%2Fgrails%2Fgradle%2Fplugin%2Fcore%2FGrailsIndyVariants.groovy&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache#diff-Z3JhaWxzLWdyYWRsZS9wbHVnaW5zL3NyYy9tYWluL2dyb292eS9vcmcvZ3JhaWxzL2dyYWRsZS9wbHVnaW4vY29yZS9HcmFpbHNJbmR5VmFyaWFudHMuZ3Jvb3Z5) | 0.0000% | [48 Missing :warning: ](https://app.codecov.io/gh/apache/grails-core/pull/16170?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) |
   | [...rails/gradle/plugin/core/GrailsGradlePlugin.groovy](https://app.codecov.io/gh/apache/grails-core/pull/16170?src=pr&el=tree&filepath=grails-gradle%2Fplugins%2Fsrc%2Fmain%2Fgroovy%2Forg%2Fgrails%2Fgradle%2Fplugin%2Fcore%2FGrailsGradlePlugin.groovy&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache#diff-Z3JhaWxzLWdyYWRsZS9wbHVnaW5zL3NyYy9tYWluL2dyb292eS9vcmcvZ3JhaWxzL2dyYWRsZS9wbHVnaW4vY29yZS9HcmFpbHNHcmFkbGVQbHVnaW4uZ3Jvb3Z5) | 0.0000% | [9 Missing :warning: ](https://app.codecov.io/gh/apache/grails-core/pull/16170?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) |
   | [...gradle/plugin/core/GrailsPluginGradlePlugin.groovy](https://app.codecov.io/gh/apache/grails-core/pull/16170?src=pr&el=tree&filepath=grails-gradle%2Fplugins%2Fsrc%2Fmain%2Fgroovy%2Forg%2Fgrails%2Fgradle%2Fplugin%2Fcore%2FGrailsPluginGradlePlugin.groovy&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache#diff-Z3JhaWxzLWdyYWRsZS9wbHVnaW5zL3NyYy9tYWluL2dyb292eS9vcmcvZ3JhaWxzL2dyYWRsZS9wbHVnaW4vY29yZS9HcmFpbHNQbHVnaW5HcmFkbGVQbHVnaW4uZ3Jvb3Z5) | 0.0000% | [3 Missing :warning: ](https://app.codecov.io/gh/apache/grails-core/pull/16170?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) |
   
   <details><summary>Additional details and impacted files</summary>
   
   
   
   [![Impacted file tree graph](https://app.codecov.io/gh/apache/grails-core/pull/16170/graphs/tree.svg?width=650&height=150&src=pr&token=qJrryhpk7u&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)](https://app.codecov.io/gh/apache/grails-core/pull/16170?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)
   
   ```diff
   @@                 Coverage Diff                 @@
   ##                8.0.x     #16170         +/-   ##
   ===================================================
   - Coverage     52.3364%   21.7155%   -30.6209%     
   + Complexity      18545        334      -18211     
   ===================================================
     Files            2039         67       -1972     
     Lines           97521       3859      -93662     
     Branches        17143        663      -16480     
   ===================================================
   - Hits            51039        838      -50201     
   + Misses          38994       2865      -36129     
   + Partials         7488        156       -7332     
   ```
   
   | [Files with missing lines](https://app.codecov.io/gh/apache/grails-core/pull/16170?dropdown=coverage&src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | Coverage Δ | |
   |---|---|---|
   | [...g/grails/gradle/plugin/core/GrailsExtension.groovy](https://app.codecov.io/gh/apache/grails-core/pull/16170?src=pr&el=tree&filepath=grails-gradle%2Fplugins%2Fsrc%2Fmain%2Fgroovy%2Forg%2Fgrails%2Fgradle%2Fplugin%2Fcore%2FGrailsExtension.groovy&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache#diff-Z3JhaWxzLWdyYWRsZS9wbHVnaW5zL3NyYy9tYWluL2dyb292eS9vcmcvZ3JhaWxzL2dyYWRsZS9wbHVnaW4vY29yZS9HcmFpbHNFeHRlbnNpb24uZ3Jvb3Z5) | `54.3478% <100.0000%> (ø)` | |
   | [...gradle/plugin/core/GrailsPluginGradlePlugin.groovy](https://app.codecov.io/gh/apache/grails-core/pull/16170?src=pr&el=tree&filepath=grails-gradle%2Fplugins%2Fsrc%2Fmain%2Fgroovy%2Forg%2Fgrails%2Fgradle%2Fplugin%2Fcore%2FGrailsPluginGradlePlugin.groovy&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache#diff-Z3JhaWxzLWdyYWRsZS9wbHVnaW5zL3NyYy9tYWluL2dyb292eS9vcmcvZ3JhaWxzL2dyYWRsZS9wbHVnaW4vY29yZS9HcmFpbHNQbHVnaW5HcmFkbGVQbHVnaW4uZ3Jvb3Z5) | `0.0000% <0.0000%> (ø)` | |
   | [...rails/gradle/plugin/core/GrailsGradlePlugin.groovy](https://app.codecov.io/gh/apache/grails-core/pull/16170?src=pr&el=tree&filepath=grails-gradle%2Fplugins%2Fsrc%2Fmain%2Fgroovy%2Forg%2Fgrails%2Fgradle%2Fplugin%2Fcore%2FGrailsGradlePlugin.groovy&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache#diff-Z3JhaWxzLWdyYWRsZS9wbHVnaW5zL3NyYy9tYWluL2dyb292eS9vcmcvZ3JhaWxzL2dyYWRsZS9wbHVnaW4vY29yZS9HcmFpbHNHcmFkbGVQbHVnaW4uZ3Jvb3Z5) | `0.0000% <0.0000%> (ø)` | |
   | [...rails/gradle/plugin/core/GrailsIndyVariants.groovy](https://app.codecov.io/gh/apache/grails-core/pull/16170?src=pr&el=tree&filepath=grails-gradle%2Fplugins%2Fsrc%2Fmain%2Fgroovy%2Forg%2Fgrails%2Fgradle%2Fplugin%2Fcore%2FGrailsIndyVariants.groovy&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache#diff-Z3JhaWxzLWdyYWRsZS9wbHVnaW5zL3NyYy9tYWluL2dyb292eS9vcmcvZ3JhaWxzL2dyYWRsZS9wbHVnaW4vY29yZS9HcmFpbHNJbmR5VmFyaWFudHMuZ3Jvb3Z5) | `0.0000% <0.0000%> (ø)` | |
   
   ... and [1973 files with indirect coverage changes](https://app.codecov.io/gh/apache/grails-core/pull/16170/indirect-changes?src=pr&el=tree-more&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)
   </details>
   <details><summary> :rocket: New features to boost your workflow: </summary>
   
   - :snowflake: [Test Analytics](https://docs.codecov.com/docs/test-analytics): Detect flaky tests, report on failures, and find test suite problems.
   - :package: [JS Bundle Analysis](https://docs.codecov.com/docs/javascript-bundle-analysis): Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@grails.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat!: make callsite caching the default and publish invokedynamic under a classifier [grails-core]

Posted by "codeconsole (via GitHub)" <gi...@apache.org>.
codeconsole closed pull request #16170: feat!: make callsite caching the default and publish invokedynamic under a classifier
URL: https://github.com/apache/grails-core/pull/16170


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@grails.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat: publish Groovy artifacts with and without invokedynamic [grails-core]

Posted by "testlens-app[bot] (via GitHub)" <gi...@apache.org>.
testlens-app[bot] commented on PR #16170:
URL: https://github.com/apache/grails-core/pull/16170#issuecomment-5336773429

   ## 🚨 TestLens detected 1 failed test 🚨
   
   Here is what you can do:
   
   1) Inspect the test failures carefully.
   2) If you are convinced that some of the tests are flaky, you can mute them below.
   3) Finally, trigger a rerun by checking the rerun checkbox.
   
   ### Test Summary
   
   #### [CI / Functional Tests \(Java 21, indy\=false, shard 1\)](https://github.com/apache/grails-core/actions/runs/32207638339/job/95933853514?pr=16170) > :grails-test-examples-app1:integrationTest
   
   | Test | Runs | Flakiness |
   |---|---|--:|
   | AsyncPromiseSpec > conditional async uses sync mode when requested | ❌ | [1%&nbsp;🟡](https://github.com/apache/grails-core/issues/16030) |
   
   🏷️ Commit: b9ed461d1baf92b705850cd39c3b69784883d794
   ▶️ Tests:  14575 executed
   🟡 Checks: 25/71 completed
   
   ### Test Failures
   
   <details>
   
   <summary><strong>AsyncPromiseSpec > conditional async uses sync mode when requested</strong> (:grails-test-examples-app1:integrationTest in <a href="https://github.com/apache/grails-core/actions/runs/32207638339/job/95933853514?pr=16170">CI / Functional Tests (Java 21, indy=false, shard 1)</a>)</summary>
   
   ```
   java.net.http.HttpTimeoutException: request timed out
   	at java.net.http/jdk.internal.net.http.HttpClientImpl.send(HttpClientImpl.java:953)
   	at java.net.http/jdk.internal.net.http.HttpClientFacade.send(HttpClientFacade.java:133)
   	at org.apache.grails.testing.http.client.HttpClientSupport$Trait$Helper.send(HttpClientSupport.groovy:1133)
   	at org.apache.grails.testing.http.client.HttpClientSupport$Trait$Helper.send(HttpClientSupport.groovy:1122)
   	at org.apache.grails.testing.http.client.HttpClientSupport$Trait$Helper.http(HttpClientSupport.groovy:203)
   	at org.apache.grails.testing.http.client.HttpClientSupport$Trait$Helper.http(HttpClientSupport.groovy:169)
   	at functionaltests.async.AsyncPromiseSpec.conditional async uses sync mode when requested(AsyncPromiseSpec.groovy:280)
   ```
   
   </details>
   
   ### Muted Tests
   > [!NOTE]
   > Checks are currently running using the configuration below.
   
   Select tests to mute in this pull request:
   
   🔲 AsyncPromiseSpec > conditional async uses sync mode when requested <!-- uniqueId=[engine:spock]/[spec:functionaltests.async.AsyncPromiseSpec]/[feature:$spock_feature_0_15] -->
   
   Reuse successful test results:
   
   🔲 ♻️ Only rerun the tests that failed or were muted before
   
   Click the checkbox to trigger a rerun:
   
   🔲 **Rerun jobs**
   
   ---
   _Learn more about TestLens at [testlens.app](https://testlens.app)._
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@grails.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat!: make callsite caching the default and publish invokedynamic under a classifier [grails-core]

Posted by "testlens-app[bot] (via GitHub)" <gi...@apache.org>.
testlens-app[bot] commented on PR #16170:
URL: https://github.com/apache/grails-core/pull/16170#issuecomment-5349704181

   ## 🚨 TestLens detected 1 failed test 🚨
   
   Here is what you can do:
   
   1) Inspect the test failures carefully.
   2) If you are convinced that some of the tests are flaky, you can mute them below.
   3) Finally, trigger a rerun by checking the rerun checkbox.
   
   ### Test Summary
   
   #### [CI - Groovy Joint Validation Build / Build Grails with Groovy snapshot \(shard 2\)](https://github.com/apache/grails-core/actions/runs/32316348453/job/96270264105?pr=16170) > :grails-data-mongodb-spring-boot:test
   
   | Test | Runs | Flakiness |
   |---|---|--:|
   | MongoDbGormAutoConfigurationSpec > Test that GORM is correctly configured | ❌ | 0%&nbsp;🟢 |
   
   🏷️ Commit: 3ce9e885be4d5c85dc9e3ad88775233f7198b310
   ▶️ Tests:  19222 executed
   🟡 Checks: 25/71 completed
   
   ### Test Failures
   
   <details>
   
   <summary><strong>MongoDbGormAutoConfigurationSpec > Test that GORM is correctly configured</strong> (:grails-data-mongodb-spring-boot:test in <a href="https://github.com/apache/grails-core/actions/runs/32316348453/job/96270264105?pr=16170">CI - Groovy Joint Validation Build / Build Grails with Groovy snapshot (shard 2)</a>)</summary>
   
   ```
   Condition failed with Exception:
   
   Person.count() != null
   |      |
   |      groovy.lang.MissingPropertyException: No such property: log for class: org.grails.datastore.gorm.mongodb.boot.autoconfigure.Person
   |      Possible solutions: age, id, DB, all
   |      	at org.grails.datastore.gorm.GormStaticApi.propertyMissing(GormStaticApi.groovy:218)
   |      	at org.grails.datastore.gorm.GormStaticApi.count_closure10(GormStaticApi.groovy:385)
   |      	at org.grails.datastore.mapping.core.DatastoreUtils.execute(DatastoreUtils.java:334)
   |      	at org.grails.datastore.gorm.AbstractGormApi.execute(AbstractGormApi.groovy:164)
   |      	at org.grails.datastore.gorm.GormStaticApi.count(GormStaticApi.groovy:381)
   |      	at org.grails.datastore.gorm.GormEntity$Trait$Helper.count(GormEntity.groovy:733)
   |      	at org.grails.datastore.gorm.mongodb.boot.autoconfigure.MongoDbGormAutoConfigurationSpec.Test that GORM is correctly configured(MongoDbGormAutoConfigurationSpec.groovy:66)
   class org.grails.datastore.gorm.mongodb.boot.autoconfigure.Person
   
   	at org.grails.datastore.gorm.mongodb.boot.autoconfigure.MongoDbGormAutoConfigurationSpec.Test that GORM is correctly configured(MongoDbGormAutoConfigurationSpec.groovy:66)
   Caused by: groovy.lang.MissingPropertyException: No such property: log for class: org.grails.datastore.gorm.mongodb.boot.autoconfigure.Person
   Possible solutions: age, id, DB, all
   	at org.grails.datastore.gorm.GormStaticApi.propertyMissing(GormStaticApi.groovy:218)
   	at org.grails.datastore.gorm.GormStaticApi.count_closure10(GormStaticApi.groovy:385)
   	at org.grails.datastore.mapping.core.DatastoreUtils.execute(DatastoreUtils.java:334)
   	at org.grails.datastore.gorm.AbstractGormApi.execute(AbstractGormApi.groovy:164)
   	at org.grails.datastore.gorm.GormStaticApi.count(GormStaticApi.groovy:381)
   	at org.grails.datastore.gorm.GormEntity$Trait$Helper.count(GormEntity.groovy:733)
   	... 1 more
   ```
   
   </details>
   
   ### Rerun Controls
   > [!NOTE]
   > Checks are currently running using the configuration below.
   
   Select tests to mute in this pull request:
   
   🔲 MongoDbGormAutoConfigurationSpec > Test that GORM is correctly configured <!-- uniqueId=[engine:spock]/[spec:org.grails.datastore.gorm.mongodb.boot.autoconfigure.MongoDbGormAutoConfigurationSpec]/[feature:$spock_feature_1_0] -->
   
   Reuse successful test results:
   
   🔲 ♻️ Only rerun the tests that failed or were muted before
   
   Click the checkbox to trigger a rerun:
   
   🔲 **Rerun jobs**
   
   ---
   _Learn more about TestLens at [testlens.app/docs](https://testlens.app/docs/features/pr-comment/)._
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@grails.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org