matrei opened a new pull request, #16393: URL: https://github.com/apache/grails-core/pull/16393
## Summary `CreateControllerCommandSpec > test app with controller` fails on every 7.0.x-based CI run of **Build Grails Forge (17)**, for example #16392 (twice) and #16390. The test generates an app, runs its `./gradlew build`, and polls the output for `BUILD SUCCESSFUL` for at most 240 seconds. On JDK 17 runners the generated app is still in `integrationTest` when the time runs out. The build hasn't regressed. The limit is too tight for the runners. Running the spec locally on JDK 17 (with the wait raised so the real duration shows): | Commit | `test app with controller` | |---|---| | `31bd1ca2b0` (last green 7.0.x run) | 50.1 s | | `86824f60ba` (current 7.0.x head) | 53.3 s | On CI runners the same test takes about 176–209 s when it passes, which leaves little headroom under 240 s. ## Changes - `CommandSpec.getDefaultPollingConditions()` waits up to 480 seconds instead of 240. This is the shared default for the generated-app build checks in the Controller, Service, Interceptor, TagLib and DomainClass command specs. Polling ends as soon as the expected text appears, so the higher limit only adds time when a generated build genuinely fails. ## Testing - `:grails-forge-cli:test` on JDK 17: 30 tests, all pass. - `:grails-forge-cli:codeStyle` passes. -- 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]
