across

Across the Great Wall we can reach every corner in the world

Runssource: GitHubhomepageShellApache-2.0commit fdb40962837b

Shell, Apache-2.0 licensed. The project labels itself: auto transfer backup, backup, bbr, benchmark, kms, l2tp, shell and unixbench.

across runs. An Argusic agent installed it in 0.2 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All 22 shell scripts in the repo pass bash syntax validation, and bench.sh executes its I/O benchmark and Ookla speedtest successfully against live servers.

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

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.04 (measured)
recorded runs
2
last tested
stars
5,371
forks
2,185
open issues
36
watchers
137
size
1 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 across, 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.

  • wget not installed; bench.sh uses hardcoded wget for speedtest download (has curl-based fallback for geo-IP only)0.3 minutes
Install time
under a minute
Cold machine to finish
7 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
bash -n on all 22 scripts exited 0; ./bench.sh ran I/O test (3 runs, avg 2013.9 MB/s) and Ookla speedtest CLI against 4 real servers returning live metrics
Model tokens used
87,041
Exact commit tested
fdb40962837b
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 verdict above comes from a different attempt, so read this as one session and not as the current result. 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.

- **`bench.sh`** was exercised end-to-end: the I/O test completed (1.8/2.1/2.0 GB/s) and the Ookla …
- The only "fix" needed was that `wget` isn't installed in this container. `bench.sh` uses hardcode…
- Most scripts (`kms.sh`, `bbr.sh`, `backup.sh`, `wireguard.sh`, `unixbench.sh`, `InstallNET.sh`) r…
- No traditional test suite exists.
tokens used
87,041
Here's what I've done and found:
- **All 22 shell scripts** pass `bash -n` syntax validation.
- **`bench.sh`** was exercised end-to-end: the I/O test completed (1.8/2.1/2.0 GB/s) and the Ookla …
- The only "fix" needed was that `wget` isn't installed in this container. `bench.sh` uses hardcode…
- Most scripts (`kms.sh`, `bbr.sh`, `backup.sh`, `wireguard.sh`, `unixbench.sh`, `InstallNET.sh`) r…
- No traditional test suite exists.

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 0.2 minutes.
  • Recovered from all 1 error 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.
  • A quick evaluation: it was running 0.2 minutes after the clone.

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/3Runs100.000.04
Argusic Runner1/3Runs100.000.05

Topics (from GitHub)

auto-transfer-backupbackupbbrbenchmarkkmsl2tpshellunixbench

Embed the badge

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

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

Questions

Does across run?
Yes. across runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test across?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit fdb40962837b. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test across?
The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does across take to install?
0.2 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 across need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing across?
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 across?
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