You are an expert in writing code in many different languages. Your goal is to perform code completion for the following code, keeping in mind the rest of the code and the file meta data.
    Metadata details:
    filename: load_balancers.rs
    path of file: ./repos/mongo-rust-driver/src/test/spec
    
    the code of the file until where you have to start completion: use crate::test::spec::{
    unified_runner::{run_unified_tests, ExpectedCmapEvent, ExpectedEvent, TestFile},
    ExpectedEventType,
};

#[tokio::test(flavor = "multi_thread")]
async fn run_unified() {
    // The Rust driver's asynchronous check-in of connections means that sometimes a new
    // conn
    
async fn run_unified() {
    // The Rust driver's asynchronous check-in of connections means that sometimes a new
    // connection will be created, rather than re-using an existing one; the connectionReady
    // events generated by this cause tests to fail, but does not break user-visible behavior.
    // TODO RUST-1055 Remove this workaround.
    fn file_transformation(test_file: &mut TestFile) {
        for test in &mut test_file.tests {
            if let Some(e) = test.expect_events.as_mut() {
                for expect_events in e {
                    if expect_events.event_type == Some(ExpectedEventType::Cmap) {
                        expect_events.event_type =
                            Some(ExpectedEventType::CmapWithoutConnectionReady);
                        expect_events.events.retain(|ev| {
                            !matches!(
                                ev,
                                ExpectedEvent::Cmap(ExpectedCmapEvent::ConnectionReady {})
                            )
                        });
                    }
                }
            }
        }
    }

    run_unified_tests(&["load-balancers"])
        // The Rust driver doesn't support wait queue timeouts.
        .skip_files(&["wait-queue-timeouts.json"])
        .transform_files(file_transformation)
        .await;
}