tox
Command line driven CI frontend and development task automation tool.
Runssource: GitHubhomepagePythonMITcommit f46060e29701
Python, MIT licensed. The project labels itself: actions, automation, cli, continuous integration, python, testing, venv and virtualenv.
tox runs. An Argusic agent installed it in 3 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
tox 4.64.3 installed in /tmp/tox-venv, 8069 tests pass across config, execute, session, plugin, journal, util, pytest_, tox_env, and docs modules; CLI launches and prints version 4.64.3
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
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.
- missing test dependencies (pytest-timeout, argcomplete, psutil, etc.)3 minutes
- pip install blocked by externally-managed-environment1 minute
- test_config_requires fails: version 0.1.dev1 doesn't satisfy tox>=41 minute
- test_schema_tombi_lint errors: tombi binary not in PATH inside test subprocess1 minute
- 3 manpage rendering tests fail in minimized container (no man-db)
- Install time
- 3 minutes
- Cold machine to finish
- 25 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- pytest ran 8151 tests (6966+378+480+154+173) across all modules; only 3 container-specific manpage rendering failures; tox --version prints 4.64.3
- Model tokens used
- 88,119
- Exact commit tested
- f46060e29701
- 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.
tokens used 88,119 Here is my complete assessment. **Install**: Created a venv, installed tox in dev mode with all test dependencies. Version resolves… **Fix summary**: 7 errors were encountered and fixed: - System pip blocked by PEP 668 → used venv - Missing `pytest-timeout`, `argcomplete`, `psutil`, and ~20 dev packages → installed from the `tes… - `test_config_requires` failed because `0.1.dev1` didn't satisfy `tox>=4` → tagged the repo `4.64.… - `tombi` binary not on PATH → prepended venv bin dir to PATH - Manpage-rendering tests fail in this minimized container (no `man-db`) — these are the only unfix… **Test results**: All 8069 tests that can run in this environment pass. The only failures are 3 man… `tox --version` prints `4.64.3 from /work/repo/src/tox/__init__.py`.
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.
- 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 MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 3 minutes to install, slower than the median of the 10 comparable projects Argusic has measured.
Of the 11 actions projects Argusic has installed and timed, tox was the 8th fastest to reach a running state, and 6 of 11 reached one at all.
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 3 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
Topics (from GitHub)
actionsautomationclicontinuous-integrationpythontestingvenvvirtualenv
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/tox)Questions
- Does tox run?
- Yes. tox runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test tox?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f46060e29701. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test tox?
- The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does tox take to install?
- 3 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 tox need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing tox?
- 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.
- How does tox compare with the alternatives?
- Of the 11 actions projects Argusic has installed and timed, tox was the 8th fastest to reach a running state, and 6 of 11 reached one at all.
- Where is the evidence for tox?
- 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.