codeconsole commented on PR #16214:
URL: https://github.com/apache/grails-core/pull/16214#issuecomment-5719689696

   Thanks @matrei. Pushed `cbad317a13`.
   
   **New finding 1 — Windows JDK 25 shard 2.** I pulled the log. It is not a 
test failure and not this PR: the Groovy compiler worker crashed.
   
   ```
   > Task :grails-geb:compileTestFixturesGroovy FAILED
   Caused by: org.gradle.process.internal.worker.WorkerProcessException: Failed 
to run Gradle Worker Daemon
   Caused by: org.gradle.process.ProcessExecutionException: Process 'Gradle 
Worker Daemon 135'
             finished with non-zero exit value -1073741571 (NTSTATUS 0xC00000FD)
   Worker daemon 'Gradle Worker Daemon 135' exited unexpectedly with exit code 
-1073741571.
   ```
   
   `0xC00000FD` is `STATUS_STACK_OVERFLOW`, so the worker JVM died compiling 
`grails-geb`'s test fixtures — a module this PR does not touch, in a step that 
runs before any of the shard's tests. The same run also logged `Connection 
reset by peer` storing to the remote build cache, which fits a struggling 
runner. Your reasoning about shard membership matches what the log shows: the 
shard reached `:grails-geb:compileTestFixturesGroovy` and never got to the 
tests.
   
   That job is running again on this head rather than being rerun on the old 
one, since the push restarts the full matrix.
   
   **New finding 2 — canary `UserControllerSpec > User list`.** Agreed, #16030, 
unrelated.
   
   **New finding 3 — anchor (nit).** Fixed. `transactions.adoc` now carries an 
explicit `[[readOnlyTransactions]]` above the subsection heading, and the three 
links point at it: `<<readOnlyTransactions,Read-Only Transactions>>` from the 
Spring Data interop page, and `{mongodb5Guide}index.html#readOnlyTransactions` 
from What's New and the upgrade guide. Rebuilt 
`:grails-data-mongodb-docs:asciidoctor`; the rendered `index.html` has 
`id="readOnlyTransactions"` on the subsection and the links now land on it.
   
   Thanks for the round-1 re-verification, particularly confirming the `and:` 
assertions measure the session close through 
`DatastoreUtils.executeWithNewSession`, and that both Hibernate 5 and 7 
managers set `MANUAL` — the docs claim parity with Hibernate, so that mattered.
   


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