jamesfredley commented on PR #15467:
URL: https://github.com/apache/grails-core/pull/15467#issuecomment-4354643342

   Triage of the two red checks on commit `0178a108c7` (in reply to TestLens 
above):
   
   ## 1. `Build Grails-Core (windows-latest, 25)` - flaky test, fix in flight
   
   The single failure (`FormTagLib2Tests > 
testDatePickerTagWithMinutePrecision()`) is unrelated to this PR's change set 
(this PR only touches `grails-gradle/`; the flaky test lives in `grails-gsp/`). 
Root cause is a race in `testDatePickerTag`: the helper rendered the picker 
HTML, **then** built a fresh `GregorianCalendar`; on slow runners the two calls 
fell on opposite sides of a minute boundary and the assertion mismatched.
   
   Tracked separately in **#15612** against `8.0.x`. Once it merges, the next 
`8.0.x` -> this branch sync will pick up the fix.
   
   ## 2. `CI - Groovy Joint Validation Build` (`build_grails`) - pre-existing 
on `8.0.x`
   
   Not introduced by this PR. The job has been failing on every push to `8.0.x` 
since 2026-04-29 with:
   
   ```
   org.spockframework.util.IncompatibleGroovyVersionException:
   The Spock compiler plugin cannot execute because Spock 2.4.0-groovy-5.0
   is not compatible with Groovy 4.0.32-SNAPSHOT.
   ```
   
   Recent `8.0.x` runs of the same workflow:
   
   - 
[25144143636](https://github.com/apache/grails-core/actions/runs/25144143636) 
(7cf1d19) - failure
   - 
[25134285481](https://github.com/apache/grails-core/actions/runs/25134285481) 
(1b33cf8) - failure
   - 
[25086923954](https://github.com/apache/grails-core/actions/runs/25086923954) 
(7174dd2) - failure
   - 
[25086897319](https://github.com/apache/grails-core/actions/runs/25086897319) 
(919802e) - failure
   - 
[25082518134](https://github.com/apache/grails-core/actions/runs/25082518134) 
(6e4c6a3) - failure
   
   The Joint Validation Build swaps Groovy to `4.0.32-SNAPSHOT` (Apache Groovy 
4 main) but the BOM now pins `spock-core:2.4-groovy-5.0` (commit ae7ee513ec, 
`Override spock to match the micronaut bom's version`). The same problem was 
already worked around for forge-generated apps in commit 5d71eb4035 via 
`-Dspock.iKnowWhatImDoing.disableGroovyVersionCheck=true`, but that bypass was 
never applied to the grails-core build itself.
   
   Filed as **#15613** with full diagnosis and three suggested remediations 
(apply the existing forge bypass to the framework build, pin Spock to a 
Groovy-4 variant for the joint matrix, or retire the Groovy 4 joint matrix). It 
cannot be fixed inside this PR.
   
   ## Status
   
   - Base branch is up to date - latest merge `0178a108c73` already includes 
`origin/8.0.x` head.
   - Once #15612 merges, please rerun CI here. Both red checks should clear 
(`build_grails` will still fail until #15613 is addressed, but it's 
pre-existing and not gating).


-- 
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