endless-sky

Space exploration, trading, and combat game.

Could not verifysource: GitHubhomepageC++GPL-3.0commit 129f3ac56eaf

C++, GPL-3.0 licensed. The project labels itself: 2d game, adventure game, arcade game, c plus plus, cpp, endless sky, exploration and free.

Argusic could not get endless-sky running. An Argusic agent installed it in 51 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Endless Sky v0.11.3.0-alpha builds and launches from /work/repo/build/linux/Release/endless-sky, printing help text and version info, with all dependencies resolved via staged .deb packages in /tmp/staging.

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 50 of 100 (the mean of this project's run scores).

At a glance

verdict
Could not verify
Argusic Score
50 / 100
cost of the verifying run
$0.44 (measured)
recorded runs
4
last tested
stars
7,581
forks
1,317
open issues
905
watchers
168
size
577 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 endless-sky, 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.

  • No development packages (headers/libs) available on bare container - library debs had to be downloaded and staged manually30 minutes
  • Missing runtime .so chains for staged dev packages (libGLEW.so.2.2.0, libavif.so.16.0.4, libSDL2-2.0.so.0.3000.0, libopenal.so.1.23.1, etc.)8 minutes
  • vcpkg bootstrap failed because the checked-out baseline (old commit) has schema-version 1 in vcpkg-tools.json but the bootstrapped binary expects version 25 minutes
  • Linker errors: missing -lasound, -lpulse, -lsamplerate, X/Wayland libs from SDL2 static dependencies3 minutes
  • Missing X11/X.h header for GLX compilation2 minutes
  • libFLAC.a compiled with ogg support but -logg not linked; ambiguous symbol ogg_stream_reset2 minutes
Install time
51 minutes
Cold machine to finish
59 minutes
Errors hit and fixed
7 hit, 7 fixed with no human help
Model tokens used
401,550
Exact commit tested
129f3ac56eaf
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.

/bin/sh -lc 'cd /work/repo && LD_LIBRARY_PATH=/tmp/staging/usr/lib/x86_64-linux-gnu timeout 5 ./bui…
 succeeded in 0ms:
Endless Sky ver. 0.11.3.0-alpha
License GPLv3+: GNU GPL version 3 or later: <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Compiled against SDL v2.30.0
Using SDL v2.30.0
The build and binary work. Now let me compile the final result.
tokens used
401,550
The build and binary work. Now let me compile the final result.

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

  • Installed in 51 minutes.
  • Recovered from all 7 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed GPL-3.0, as reported by its host.
  • 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.

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.08
Argusic Runner1/3Unverified80.000.44
Argusic Runner2/3Ran out of time0.000.42
Argusic Runner1/3Ran out of time0.000.14

Topics (from GitHub)

2d-gameadventure-gamearcade-gamec-plus-pluscppendless-skyexplorationfreegamegame-developmentgamedevindiemoddingmultiplatformopen-sourceopenglopensourcerpgspacetop-down

Embed the badge

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

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

Questions

Does endless-sky run?
Argusic could not verify that endless-sky runs. Argusic installed and launched it on a clean machine in 51 minutes, hitting 7 errors on the way, and recorded the session.
How did Argusic test endless-sky?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 129f3ac56eaf. 4 attempts are recorded, and the full method is on the methodology page.
What did it cost to test endless-sky?
The run that produced this verdict cost $0.44: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does endless-sky 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 endless-sky need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing endless-sky?
7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for endless-sky?
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.

Discussion