testlens-app[bot] commented on PR #16117:
URL: https://github.com/apache/grails-core/pull/16117#issuecomment-5228306350

   ## 🚨 TestLens detected 3 failed tests 🚨
   
   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 / Build Grails Forge \(Java 21, 
indy\=true\)](https://github.com/apache/grails-core/actions/runs/31279121645/job/93157471503?pr=16117)
 > :grails-forge-cli:test [grails-forge]
   
   | Test | Runs | Flakiness |
   |---|---|--:|
   | CreateControllerCommandSpec > test app with controller | ❌ | 
[1% 🟡](https://github.com/apache/grails-core/issues/16030) |
   | CreateDomainClassCommandSpec > test app with domain | ❌ | 0% 🟢 |
   
   #### [CI / Build Grails Forge \(Java 21, 
indy\=true\)](https://github.com/apache/grails-core/actions/runs/31279121645/job/93157471503?pr=16117)
 > :test-core:test [grails-forge]
   
   | Test | Runs | Flakiness |
   |---|---|--:|
   | CreateRestApiSpec > test rest-api app with default json-views | ❌ | 
0% 🟢 |
   
   🏷️ Commit: f3ea64343d74fa5ae8de58a087dd7f027cffa6ae
   ▶️ Tests:  728 executed
   🟡 Checks: 51/57 completed
   
   ### Test Failures
   
   <details>
   
   <summary><strong>CreateControllerCommandSpec > test app with 
controller</strong> (:grails-forge-cli:test [grails-forge] in <a 
href="https://github.com/apache/grails-core/actions/runs/31279121645/job/93157471503?pr=16117";>CI
 / Build Grails Forge (Java 21, indy=true)</a>)</summary>
   
   ```
   Condition failed with Exception:
   
   testOutputContains('BUILD SUCCESSFUL')
   |
   java.lang.AssertionError: The generated build exited with code 1 without 
producing the expected output [BUILD SUCCESSFUL].
   Build output:
   To honour the JVM settings for this build a single-use Daemon process will 
be forked. For more on this, please refer to 
https://docs.gradle.org/9.7.0/userguide/gradle_daemon.html#sec:disabling_the_daemon
 in the Gradle documentation.
   Daemon will be stopped at the end of the build 
   gradle/actions: Writing build results to 
/home/runner/work/_temp/.gradle-actions/build-results/__run_3-1786225080228.json
    
   [Incubating] Problems report is available at: 
file:///tmp/grailsforgetmp8066314523740886675/build/reports/problems/problems-report.html
    
   Deprecated Gradle features were used in this build, making it incompatible 
with Gradle 10.
    
   You can use '--warning-mode all' to show the individual deprecation warnings 
and determine if they come from your own scripts or plugins.
    
   For more on this, please refer to 
https://docs.gradle.org/9.7.0/userguide/command_line_interface.html#sec:command_line_warnings
 in the Gradle documentation.
    
        at 
org.grails.forge.cli.CommandSpec.testOutputContains(CommandSpec.groovy:101)
        at org.grails.forge.cli.command.CreateControllerCommandSpec.test app 
with controller(CreateControllerCommandSpec.groovy:73)
   
        at org.grails.forge.cli.command.CreateControllerCommandSpec.test app 
with controller(CreateControllerCommandSpec.groovy:73)
   Caused by: java.lang.AssertionError: The generated build exited with code 1 
without producing the expected output [BUILD SUCCESSFUL].
   Build output:
   To honour the JVM settings for this build a single-use Daemon process will 
be forked. For more on this, please refer to 
https://docs.gradle.org/9.7.0/userguide/gradle_daemon.html#sec:disabling_the_daemon
 in the Gradle documentation.
   Daemon will be stopped at the end of the build 
   gradle/actions: Writing build results to 
/home/runner/work/_temp/.gradle-actions/build-results/__run_3-1786225080228.json
   
   [Incubating] Problems report is available at: 
file:///tmp/grailsforgetmp8066314523740886675/build/reports/problems/problems-report.html
   
   Deprecated Gradle features were used in this build, making it incompatible 
with Gradle 10.
   
   You can use '--warning-mode all' to show the individual deprecation warnings 
and determine if they come from your own scripts or plugins.
   
   For more on this, please refer to 
https://docs.gradle.org/9.7.0/userguide/command_line_interface.html#sec:command_line_warnings
 in the Gradle documentation.
   
        at 
org.grails.forge.cli.CommandSpec.testOutputContains(CommandSpec.groovy:101)
        ... 1 more
   ```
   
   </details>
   <details>
   
   <summary><strong>CreateDomainClassCommandSpec > test app with 
domain</strong> (:grails-forge-cli:test [grails-forge] in <a 
href="https://github.com/apache/grails-core/actions/runs/31279121645/job/93157471503?pr=16117";>CI
 / Build Grails Forge (Java 21, indy=true)</a>)</summary>
   
   ```
   Condition failed with Exception:
   
   testOutputContains("BUILD SUCCESSFUL")
   |
   java.lang.AssertionError: The generated build exited with code 1 without 
producing the expected output [BUILD SUCCESSFUL].
   Build output:
   To honour the JVM settings for this build a single-use Daemon process will 
be forked. For more on this, please refer to 
https://docs.gradle.org/9.7.0/userguide/gradle_daemon.html#sec:disabling_the_daemon
 in the Gradle documentation.
   Daemon will be stopped at the end of the build 
   gradle/actions: Writing build results to 
/home/runner/work/_temp/.gradle-actions/build-results/__run_3-1786225142280.json
    
   [Incubating] Problems report is available at: 
file:///tmp/grailsforgetmp12567884874334993568/build/reports/problems/problems-report.html
    
   Deprecated Gradle features were used in this build, making it incompatible 
with Gradle 10.
    
   You can use '--warning-mode all' to show the individual deprecation warnings 
and determine if they come from your own scripts or plugins.
    
   For more on this, please refer to 
https://docs.gradle.org/9.7.0/userguide/command_line_interface.html#sec:command_line_warnings
 in the Gradle documentation.
    
        at 
org.grails.forge.cli.CommandSpec.testOutputContains(CommandSpec.groovy:101)
        at org.grails.forge.cli.command.CreateDomainClassCommandSpec.test app 
with domain(CreateDomainClassCommandSpec.groovy:86)
   
        at org.grails.forge.cli.command.CreateDomainClassCommandSpec.test app 
with domain(CreateDomainClassCommandSpec.groovy:86)
   Caused by: java.lang.AssertionError: The generated build exited with code 1 
without producing the expected output [BUILD SUCCESSFUL].
   Build output:
   To honour the JVM settings for this build a single-use Daemon process will 
be forked. For more on this, please refer to 
https://docs.gradle.org/9.7.0/userguide/gradle_daemon.html#sec:disabling_the_daemon
 in the Gradle documentation.
   Daemon will be stopped at the end of the build 
   gradle/actions: Writing build results to 
/home/runner/work/_temp/.gradle-actions/build-results/__run_3-1786225142280.json
   
   [Incubating] Problems report is available at: 
file:///tmp/grailsforgetmp12567884874334993568/build/reports/problems/problems-report.html
   
   Deprecated Gradle features were used in this build, making it incompatible 
with Gradle 10.
   
   You can use '--warning-mode all' to show the individual deprecation warnings 
and determine if they come from your own scripts or plugins.
   
   For more on this, please refer to 
https://docs.gradle.org/9.7.0/userguide/command_line_interface.html#sec:command_line_warnings
 in the Gradle documentation.
   
        at 
org.grails.forge.cli.CommandSpec.testOutputContains(CommandSpec.groovy:101)
        ... 1 more
   ```
   
   </details>
   <details>
   
   <summary><strong>CreateRestApiSpec > test rest-api app with default 
json-views</strong> (:test-core:test [grails-forge] in <a 
href="https://github.com/apache/grails-core/actions/runs/31279121645/job/93157471503?pr=16117";>CI
 / Build Grails Forge (Java 21, indy=true)</a>)</summary>
   
   ```
   org.gradle.testkit.runner.UnexpectedBuildFailure: Unexpected build execution 
failure in /tmp/testrestapi17899113525225615974 with arguments [build]
   
   Output:
   
   FAILURE: Build failed with an exception.
   
   * What went wrong:
   Could not determine the dependencies of task ':compileGroovy'.
   > Task with name 'generateGrailsGroovyCompilerConfigForCompileGroovy' not 
found in root project 'testrestapi17899113525225615974'.
   
   * Try:
   > Run with --stacktrace option to get the stack trace.
   > Run with --info or --debug option to get more log output.
   > Run with --scan to get full insights from a Build Scan (powered by 
Develocity).
   > Get more help at https://help.gradle.org.
   
   BUILD FAILED in 1m 19s
   
        at 
org.gradle.testkit.runner.internal.DefaultGradleRunner.lambda$build$0(DefaultGradleRunner.java:275)
        at 
org.gradle.testkit.runner.internal.DefaultGradleRunner.run(DefaultGradleRunner.java:374)
        at 
org.gradle.testkit.runner.internal.DefaultGradleRunner.build(DefaultGradleRunner.java:273)
        at 
org.grails.forge.utils.CommandSpec.executeGradle(CommandSpec.groovy:79)
        at org.grails.forge.create.CreateRestApiSpec.test rest-api app with 
default json-views(CreateRestApiSpec.groovy:30)
   ```
   
   </details>
   
   ### Muted Tests
   > [!NOTE]
   > Checks are currently running using the configuration below.
   
   Select tests to mute in this pull request:
   
   🔲 CreateControllerCommandSpec > test app with controller <!-- 
uniqueId=[engine:spock]/[spec:org.grails.forge.cli.command.CreateControllerCommandSpec]/[feature:$spock_feature_1_1]
 -->
   🔲 CreateDomainClassCommandSpec > test app with domain <!-- 
uniqueId=[engine:spock]/[spec:org.grails.forge.cli.command.CreateDomainClassCommandSpec]/[feature:$spock_feature_1_1]
 -->
   🔲 CreateRestApiSpec > test rest-api app with default json-views <!-- 
uniqueId=[engine:spock]/[spec:org.grails.forge.create.CreateRestApiSpec]/[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](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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to