arangodb-java-driver
The official ArangoDB Java driver.
Runssource: GitHubJavaApache-2.0commit ea380b222f05
Java, Apache-2.0 licensed. The project labels itself: arangodb, database, driver, java, nosql and vpack.
arangodb-java-driver runs. An Argusic agent installed it in 14.5 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The ArangoDB Java Driver compiles from source and all core collection/document tests pass against a live ArangoDB 3.12.4 server, confirming HTTP_JSON protocol for both sync and async APIs works correctly on an end-to-end basis
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 60 of 100 (the mean of this project's run scores).
At a glance
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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- No ArangoDB database available in container4 minutes
- No Java JDK or Maven installed in container3 minutes
- arangod kept dying after a few seconds when started as background child process3 minutes
- arango.properties pointed at 172.28.0.1:8529 (Docker internal network)1 minute
- JWT/auth tests fail with auth disabled on server
- Install time
- 15 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- mvn -pl test-functional -am verify -Dit.test=ArangoCollectionTest,ArangoCollectionAsyncTest -Dfailsafe.failIfNoSpecifiedTests=false -Dgpg.skip=true -Dmaven.javadoc.skip=true exited 0, 1666 tests passed, 0 failures, 0 errors
- Model tokens used
- 389,181
- Exact commit tested
- ea380b222f05
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
"msg": "JWT/auth tests fail with auth disabled on server",
"fix": "Expected behavior - /_open/auth endpoint only exists when authentication is enabled o…
"minutes": 0
}
],
"test_depth": "tier1_real",
"notes": "Full project compiles with mvn test-compile. Ran ArangoCollectionTest (839 tests) and A…
"verified_how": "mvn -pl test-functional -am verify -Dit.test=ArangoCollectionTest,ArangoCollecti…
"final_state": "The ArangoDB Java Driver compiles from source and all core collection/document te…
}
tokens used
389,181Replay 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 14.5 minutes.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- 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 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.14 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.49 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/arangodb-java-driver)Questions
- Does arangodb-java-driver run?
- Yes. arangodb-java-driver runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test arangodb-java-driver?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ea380b222f05. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test arangodb-java-driver?
- The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does arangodb-java-driver take to install?
- 14.5 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 arangodb-java-driver need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing arangodb-java-driver?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for arangodb-java-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.