Argusic could not verify that tsurugidb runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 1 error on the way, and recorded the session.

How did Argusic test tsurugidb?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 555e8160047c. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test tsurugidb?

The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does tsurugidb take to install?

11 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 tsurugidb need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing tsurugidb?

1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for tsurugidb?

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.

tsurugidb

Tsurugi - next generation RDB for the new era

Could not verifysource: GitHub homepageShellApache-2.0commit 555e8160047c

Shell, Apache-2.0 licensed. The project labels itself: database, dbms, in memory database, many core, oltp, relational database, serializable and sql.

Argusic could not get tsurugidb running. An Argusic agent installed it in 11 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Nothing works: the C++ build fails at cmake configuration due to missing mpdec++ and every other system dependency; the Python client loads but cannot connect because no server binary exists; no Docker or root access is available to install prerequisites.
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 20 of 100 (the mean of this project's run scores).

At a glance

verdict: Could not verify
Argusic Score: 20 / 100
cost of the verifying run: $0.05 (measured)
recorded runs: 2
last tested: 2026-09-10
stars: 419
forks: 12
open issues: 4
watchers: 13
size: 1 MB
created: 2023-09-18
last push: 2026-09-23

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-23. 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.

The environment (Ubuntu 24.04, x86_64 container as user 'runner' with no root/sudo and no docker) lacks all 27+ system packages required to build Tsurugi from source: Boost (libboost-container-dev, libboost-filesystem-dev, libboost-regex-dev, libboost-serialization-dev, libboost-system-dev, libboost-thread-dev), gRPC (libgrpc-dev, libgrpc++-dev, protobuf-compiler-grpc), protobuf (libprotobuf-dev, protobuf-compiler), abseil (libabsl-dev), gflags (libgflags-dev), glog (libgoogle-glog-dev), jemalloc (libjemalloc-dev), TBB (libtbb-dev), msgpack (libmsgpack-dev), nlohmann-json (nlohmann-json3-dev), leveldb (libleveldb-dev), rocksdb (librocksdb-dev), Apache Arrow/Parquet (libarrow-dev, libparquet-dev), JWT (libjwt-dev), PostgreSQL (libpq-dev), OpenJDK 17 (openjdk-17-jdk-headless), mpdec (libmpdec++-dev), ICU (libicu-dev), UUID (uuid-dev), bison, flex, doxygen, lsb-release, ninja-build. Only gcc 13.3, cmake 3.28, make, curl, libssl-dev, and pkg-config are present.

Install time: 11 minutes
Cold machine to finish: 8 minutes
Errors hit and fixed: 1 hit, 1 fixed with no human help
Model tokens used: 62,757
Exact commit tested: 555e8160047c
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.

How the result was proved: the agent reported that it did not verify the output
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
Whether it works at all: this run verified nothing, so this page makes no claim either way

The end of the recording

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

  - arrow/parquet
  - OpenJDK 17
  - mpdec
  - JWT
  - libpq
  - ninja-build
  - bison/flex
  - uuid-dev
Here is the report.
tokens used
62,757
Here is the report.

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

Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
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

An agent with no time limit did not get it running.
Took 11 minutes to install, slower than the median of the 13 comparable projects Argusic has measured.

Of the 14 database projects Argusic has installed and timed, tsurugidb was the 13th fastest to reach a running state, and 13 of 14 reached one at all.

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	Did not run	20.00	0.05	2026-09-10 05:36 UTC
Argusic Runner	1/3	Did not run	20.00	0.27	2026-09-09 18:02 UTC

Topics (from GitHub)

database dbms in-memory-database many-core oltp relational-database serializable sql transaction tsurugidb

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/tsurugidb.svg)](https://argusic.com/subject/tsurugidb)

Questions

Does tsurugidb run?: Argusic could not verify that tsurugidb runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test tsurugidb?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 555e8160047c. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test tsurugidb?: The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does tsurugidb take to install?: 11 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 tsurugidb need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing tsurugidb?: 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does tsurugidb compare with the alternatives?: Of the 14 database projects Argusic has installed and timed, tsurugidb was the 13th fastest to reach a running state, and 13 of 14 reached one at all.
Where is the evidence for tsurugidb?: 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.