mongo-c-driver

The Official MongoDB driver for C language

Runssource: GitHubhomepageCApache-2.0commit 4ce399222e21

C, Apache-2.0 licensed. The project labels itself: mongodb, mongodb driver and nosql.

mongo-c-driver runs. An Argusic agent installed it in 15 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.

The project configures, builds, and installs into /tmp/install-prefix, and the installed libbson2/libmongoc2 libraries, exercised through a compiled consumer plus the live test suite against a real MongoDB 8.0.6 server on 127.0.0.1:27017, successfully ran a ping and CRUD/transaction/server-selection tests, with the only failures being two IPv6 tests that cannot connect because the container has no IPv6 and one SSL-re...

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 56.7 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
56.7 / 100
cost of the verifying run
$0.10 (measured)
recorded runs
2
last tested
stars
883
forks
477
open issues
17
watchers
75
size
285 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing mongo-c-driver, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • 7 crud/unified *-errorResponse tests failed: no such command 'configureFailPoint' (mongod started without test commands)10 minutes
  • 3 Client tests fail: /Client/ipv6/single, /Client/ipv6/pooled (no IPv6 in container; cannot reach [::1]:27017) and /Client/ssl/reconnect/pooled (expects 'Failed to buffer 4 bytes' log line not emitted)5 minutes
  • cmake --install failed: libbson2.so.2.6.0 missing (only test target had been built)3 minutes
Install time
15 minutes
Cold machine to finish
23 minutes
Errors hit and fixed
3 hit, 2 fixed with no human help
How the result was proved
test-libmongoc -F JSON summaries against live mongod 8.0.6 (crud PASS=123 FAIL=0; sd/sel/transactions/sessions PASS=508 FAIL=0; bson+Client+Collection+Cursor PASS=779 FAIL=3); downstream consumer program compiled against installed libs via pkg-config ran ./consumer -> 'cmd_ok=1 db_ok=1.000000 err=[]' exit 0
Model tokens used
75,807
Exact commit tested
4ce399222e21
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

I've completed the mission with thorough end-to-end verification. Here is my report.
**Summary of work done:**
- **Project:** `mongo-c-driver` 2.6.0-dev (libmongoc + libbson)
- **Configured** Debug build in `cmake-build/` per AGENTS.md; built full project and `test-libmongo…
- **Standard install** to `/tmp/install-prefix` succeeded (static + shared libs for `libbson2`/`lib…
- **No mongod present** in the container, so I downloaded MongoDB 8.0.6 and stood it up on `127.0.0…
- **Errors found & fixed:**
  1. Initial `cmake --install` failed (`libbson2.so.2.6.0` missing) because only the test target wa…
  2. 7 `crud/unified *-errorResponse` tests failed with `no such command: 'configureFailPoint'` bec…
  3. 3 `Client` tests remain failing — 2 IPv6 (`/Client/ipv6/single`, `/Client/ipv6/pooled`): the c…
- **Tier1 real verification** against live mongod 8.0.6: crud/unified 123 pass / 0 fail; server-dis…
- **Downstream consumer proof:** compiled a test program against the installed libs via pkg-config;…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 15 minutes, faster than the median of the 6 comparable projects Argusic has measured.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Hit 3 errors during setup, 1 of which were not solved.

Of the 7 c projects Argusic has installed and timed, mongo-c-driver was the 3rd fastest to reach a running state, and 6 of 7 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Did not run20.000.06
Argusic Runner1/3Runs93.330.10

Topics (from GitHub)

cmongodbmongodb-drivernosql

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/mongo-c-driver.svg)](https://argusic.com/subject/mongo-c-driver)

Questions

Does mongo-c-driver run?
Yes. mongo-c-driver runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test mongo-c-driver?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4ce399222e21. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test mongo-c-driver?
The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does mongo-c-driver take to install?
15 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does mongo-c-driver need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing mongo-c-driver?
3 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does mongo-c-driver compare with the alternatives?
Of the 7 c projects Argusic has installed and timed, mongo-c-driver was the 3rd fastest to reach a running state, and 6 of 7 reached one at all.
Where is the evidence for mongo-c-driver?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion