mongo-rust-driver Validation Report¶
Measured 2026-10-15 (raw artifact), generated 2026-10-15 — SecantusDB 0.7.0b3 vs mongo-rust-driver 12dd49b (vendor/mongo-rust-driver/).
Run uv run python -m invoke validate-rust to refresh. The Rust-driver analogue of the pymongo / mongo-go-driver / mongo-node-driver / mongo-java-driver / mongo-ruby-driver gauges — the language MongoDB consumers reach for when they want native performance + async.
Summary¶
Module |
Passed |
Failed |
Ignored |
Total |
Pass rate |
|---|---|---|---|---|---|
|
12 |
0 |
0 |
12 |
100.0% |
|
6 |
0 |
0 |
6 |
100.0% |
|
35 |
1 |
0 |
36 |
97.2% |
|
6 |
0 |
0 |
6 |
100.0% |
|
12 |
0 |
0 |
12 |
100.0% |
|
5 |
0 |
0 |
5 |
100.0% |
|
7 |
0 |
0 |
7 |
100.0% |
|
21 |
0 |
0 |
21 |
100.0% |
Overall |
104 |
1 |
0 |
105 |
99.0% |
Failures (1)¶
First 30 failed tests for triage:
test::coll::find_one_and_delete_hint_server_version
thread 'test::coll::find_one_and_delete_hint_server_version' (10170) panicked at driver/src/test/coll.rs:663:9:
How this is generated¶
invoke validate-rust spawns a SecantusDB daemon on a fresh ephemeral port, runs cargo test --lib -p mongodb against the curated include set with MONGODB_URI explicitly overridden in the subprocess env (so the user’s ambient env can’t leak through to a real mongod), parses cargo’s per-test output, and writes this report. The list of in-scope tests lives in rust_validation/include_paths.py.