Function finish_module_test

crates/testing/src/modules.rs:349–364

These standalone module tests run a `StandaloneEnv` in-process. That means [`CompiledModule::with_module_async`] and [`CompiledModule::with_module`] own the Tokio runtime, host controller, module host, scheduler, `RelationalDB`, JS worker threads, etc. Some modules schedule repeating reducers during `init`. If these helpers return without explicitly shutting the database down, scheduled reducer c

(env: &StandaloneEnv, db_identity: Identity, test_result: std::thread::Result<()>)

/// asks the host controller to exit the module host, closes and waits for the scheduler,
/// and then shuts down the `RelationalDB`.
async fn finish_module_test(env: &StandaloneEnv, db_identity: Identity, test_result: std::thread::Result<()>) {
    let cleanup_result = env.delete_database(&Identity::ZERO, &db_identity).await;

    // Cleanup should not hide the result of the test body.
    // If the test already panicked, resume that panic after attempting shutdown.
    // If the test passed, make cleanup failure a test failure.
    match (test_result, cleanup_result) {
        (Ok(()), Ok(())) => {}
        (Ok(()), Err(err)) => panic!("failed to delete test database {db_identity}: {err:#}"),
        (Err(panic), Ok(())) => std::panic::resume_unwind(panic),
        (Err(panic), Err(err)) => {
            log::error!("failed to delete test database {db_identity} after test panic: {err:#}");
            std::panic::resume_unwind(panic);
        }
    }
}

/// For testing, persist to disk by default, as many tests
/// exercise functionality like restarting the database.