0ad
[DEPRECATED] Git mirror of the 0 A.D. SVN source code (migrated to https://gitea.wildfiregames.com on August 20th 2024)
Could not verifysource: GitHubhomepageC++NOASSERTIONarchived upstreamcommit 61a3b9507d97
C++, NOASSERTION licensed.
Argusic could not get 0ad running. An Argusic agent installed it in 51 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The 0 A.D. pyrogenesis binary from the Ubuntu package launches and responds to --version. Premake5 build system, FCollada, and NVTT are built for Linux. Build makefiles are generated. SpiderMonkey could not be compiled from source due to Python dependency chain issues in the Mozilla build system.
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 18.6 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.
- SpiderMonkey mozjs-91 build failed: the Mozilla build system requires many Python dependencies not available (mozversioncontrol, mozprocess, mozfile, etc.) and creating a working Python virtualenv failed. The bundled source tarball was extracted, patches applied, and configure ran successfully, but config_status (generate makefiles) step failed due to missing mozbuild Python modules.40 minutes
- Missing development headers for SDL2, libcurl, libxml2, freetype2, OpenAL, etc. No root access to install packages via apt.10 minutes
- Install time
- 51 minutes
- Cold machine to finish
- 61 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- Model tokens used
- 639,827
- Exact commit tested
- 61a3b9507d97
- 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
- runs before 2026-09-07 did not record the command used to check the result
- 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.
The critical issue is SpiderMonkey. The project needs mozjs-91 which requires a complex Mozilla bui… Let me finalize: exec /bin/sh -lc '# Get elapsed time estimate echo "Started ~18:59, now $(date +%H:%M)" echo "About 50-55 minutes elapsed"' in /work/repo succeeded in 0ms: Started ~18:59, now 19:50 About 50-55 minutes elapsed 2026-09-05T19:51:07.127433Z ERROR codex_core::session: failed to record rollout items: thread 01a07… tokens used 639,827
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 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Measured 4 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 51 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
- Its license file could not be classified automatically, so check it yourself before using it.
Of the 4 C++ projects Argusic has installed and timed, 0ad was the 4th fastest to reach a running state, and 2 of 4 reached one at all.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Did not run | 17.14 | 0.28 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.55 | |
| Argusic Runner | 2/3 | Ran out of time | 0.00 | 0.37 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.39 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/0ad)Questions
- Does 0ad run?
- Argusic could not verify that 0ad runs. Argusic installed and launched it on a clean machine in 51 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test 0ad?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 61a3b9507d97. 4 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test 0ad?
- The run that produced this verdict cost $0.55: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does 0ad take to install?
- 51 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 0ad need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing 0ad?
- 2 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 0ad compare with the alternatives?
- Of the 4 C++ projects Argusic has installed and timed, 0ad was the 4th fastest to reach a running state, and 2 of 4 reached one at all.
- Where is the evidence for 0ad?
- All 4 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.