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

   ## 🚨 TestLens detected 2 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 / Functional Tests \(Java 25, indy\=false, shard 
1\)](https://github.com/apache/grails-core/actions/runs/35029910467/job/104585724594?pr=16345)
 > :grails-test-examples-app1:integrationTest
   
   | Test | Runs | Flakiness |
   |---|---|--:|
   | AsyncPromiseSpec > async task with timeout completes within time limit > 
async task with timeout completes within time limit [delay: 100, timeout: 500, 
elapsedMin: 100, status: completed, result: Completed in time, <span>#</span>0] 
| ❌ | [1%&nbsp;🟡](https://github.com/apache/grails-core/issues/16030) |
   | AsyncPromiseSpec > multi-stage process reports all stages | ❌ | 0%&nbsp;🟢 |
   
   🏷️ Commit: 916fefe0ac1d27e8c550afc6a1dafb2688f7b12c
   ▶️ Tests:  12933 executed
   🟡 Checks: 28/78 completed
   
   ### Test Failures
   
   <details><summary><strong>AsyncPromiseSpec > async task with timeout 
completes within time limit > async task with timeout completes within time 
limit [delay: 100, timeout: 500, elapsedMin: 100, status: completed, result: 
Completed in time, <span>#</span>0]</strong> 
(:grails-test-examples-app1:integrationTest in <a 
href="https://github.com/apache/grails-core/actions/runs/35029910467/job/104585724594?pr=16345";>CI
 / Functional Tests (Java 25, indy=false, shard 1)</a>)</summary>
   
   ```
   Condition failed with Exception:
   
   response.assertStatus(200)
   |        |
   |        org.opentest4j.AssertionFailedError: HTTP Status differs
   |            at 
org.apache.grails.testing.http.client.TestHttpResponse.verify(TestHttpResponse.groovy:980)
   |            at 
org.apache.grails.testing.http.client.TestHttpResponse.verifyStatus(TestHttpResponse.groovy:840)
   |            at 
org.apache.grails.testing.http.client.TestHttpResponse.assertStatus(TestHttpResponse.groovy:174)
   |            at functionaltests.async.AsyncPromiseSpec.async task with 
timeout completes within time limit(AsyncPromiseSpec.groovy:119)
   <org.apache.grails.testing.http.client.TestHttpResponse@51b25bfd 
delegate=inaccessible jsonSlurperConfig=inaccessible 
xmlSlurperConfig=inaccessible>
   
        at functionaltests.async.AsyncPromiseSpec.async task with timeout 
completes within time limit(AsyncPromiseSpec.groovy:119)
   Caused by: org.opentest4j.AssertionFailedError: HTTP Status differs
        at 
org.apache.grails.testing.http.client.TestHttpResponse.verify(TestHttpResponse.groovy:980)
        at 
org.apache.grails.testing.http.client.TestHttpResponse.verifyStatus(TestHttpResponse.groovy:840)
        at 
org.apache.grails.testing.http.client.TestHttpResponse.assertStatus(TestHttpResponse.groovy:174)
        ... 1 more
   ```
   
   </details>
   <details><summary><strong>AsyncPromiseSpec > multi-stage process reports all 
stages</strong> (:grails-test-examples-app1:integrationTest in <a 
href="https://github.com/apache/grails-core/actions/runs/35029910467/job/104585724594?pr=16345";>CI
 / Functional Tests (Java 25, indy=false, shard 1)</a>)</summary>
   
   ```
   Condition failed with Exception:
   
   response.assertJsonContains(200, [ status     : 'completed', totalStages: 3, 
stages     : [ [action: 'initialize'], [action: 'process'], [action: 
'finalize'] ] ])
   |        |
   |        org.opentest4j.AssertionFailedError: HTTP Status differs
   |            at 
org.apache.grails.testing.http.client.TestHttpResponse.verify(TestHttpResponse.groovy:980)
   |            at 
org.apache.grails.testing.http.client.TestHttpResponse.verifyStatus(TestHttpResponse.groovy:840)
   |            at 
org.apache.grails.testing.http.client.TestHttpResponse.assertJsonContains(TestHttpResponse.groovy:535)
   |            at 
org.apache.grails.testing.http.client.TestHttpResponse.assertJsonContains(TestHttpResponse.groovy:511)
   |            at functionaltests.async.AsyncPromiseSpec.multi-stage process 
reports all stages(AsyncPromiseSpec.groovy:240)
   <org.apache.grails.testing.http.client.TestHttpResponse@11336197 
delegate=inaccessible jsonSlurperConfig=inaccessible 
xmlSlurperConfig=inaccessible>
   
        at functionaltests.async.AsyncPromiseSpec.multi-stage process reports 
all stages(AsyncPromiseSpec.groovy:240)
   Caused by: org.opentest4j.AssertionFailedError: HTTP Status differs
        at 
org.apache.grails.testing.http.client.TestHttpResponse.verify(TestHttpResponse.groovy:980)
        at 
org.apache.grails.testing.http.client.TestHttpResponse.verifyStatus(TestHttpResponse.groovy:840)
        at 
org.apache.grails.testing.http.client.TestHttpResponse.assertJsonContains(TestHttpResponse.groovy:535)
        at 
org.apache.grails.testing.http.client.TestHttpResponse.assertJsonContains(TestHttpResponse.groovy:511)
        ... 1 more
   ```
   
   </details>
   
   ### Rerun Controls
   > [!NOTE]
   > Checks are currently running using the configuration below.
   
   Select tests to mute in this pull request:
   
   🔲 AsyncPromiseSpec > async task with timeout completes within time limit 
<!-- 
uniqueId=[engine:spock]/[spec:functionaltests.async.AsyncPromiseSpec]/[feature:$spock_feature_0_5]
 -->
   🔲 AsyncPromiseSpec > multi-stage process reports all stages <!-- 
uniqueId=[engine:spock]/[spec:functionaltests.async.AsyncPromiseSpec]/[feature:$spock_feature_0_12]
 -->
   
   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: [email protected]

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

Reply via email to