You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@grails.apache.org by GitBox <gi...@apache.org> on 2026/08/21 19:57:45 UTC

[GH] (grails-core/fix/embedded-mongo-double-stop): Workflow run "CI - Groovy Joint Validation Build" failed!

The GitHub Actions job "CI - Groovy Joint Validation Build" on grails-core.git/fix/embedded-mongo-double-stop has failed.
Run started by GitHub user codeconsole (triggered by codeconsole).

Head commit for run:
3cb9462e0f982dc608915b037ec942b9cd5ec2a7 / Scott Murphy <sc...@alwaysvip.com>
Stop the embedded MongoDB once

The lifecycle bean stops the server when the application context closes, and the
JVM shutdown hook - which is there for a context that never closes - stops it
again when the process exits. Flapdoodle removes the process directory as it tears
the server down, so the second teardown failed on the files the first one had
already deleted, and every run of an application or a test that uses a real mongod
ended with a TearDownException on a shutdown thread. CI reports it as an error
against a build whose tests all passed.

Stopping the flapdoodle server is idempotent now, as stopping the in-memory one
already was, and so is starting one that is already running. Both are covered.

Report URL: https://github.com/apache/grails-core/actions/runs/32515232608

With regards,
GitHub Actions via GitBox