setup-php
GitHub action to set up PHP with extensions, php.ini configuration, coverage drivers, and various tools.
Runs with mockssource: GitHubhomepageTypeScriptMITcommit f3d967b8bc6d
TypeScript, MIT licensed. The project labels itself: code coverage, composer, continuous integration, github actions, php, php extensions, static analysis and tools.
setup-php runs, with stand-ins for the services it depends on. An Argusic agent installed it in 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 9 test suites pass with 605/605 tests passing; npm install and tsc build succeed; the only fix needed was replacing two .toSorted() calls with .sort() for Node 18 compatibility
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 92 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.
- Array.prototype.toSorted() not available in Node 18 - ES2024 method0.5 minutes
- Install time
- 2 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm test exited 0, 605 passed across 9 suites with 100% statement/branch/function/line coverage
- Model tokens used
- 41,252
- Exact commit tested
- f3d967b8bc6d
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
/bin/sh -lc "rg -n 'toSorted' src/tools.ts" in /work/repo
exited 1 in 0ms:
The fix is clean. All 605 tests pass. Let me now build the final result.
exec
/bin/sh -lc 'date +%s' in /work/repo
succeeded in 0ms:
1790860886
<script></script>ARGUSIC_RESULT: {"install_succeeded": true, "launch_succeeded": true, "install_min…
2026-10-01T13:21:47.043701Z ERROR codex_core::session: failed to record rollout items: thread 01a0f…
tokens used
41,252
<script></script>ARGUSIC_RESULT: {"install_succeeded": true, "launch_succeeded": true, "install_min…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 2 minutes.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 | 1/3 | Runs with mocks | 92.00 | 0.02 |
Topics (from GitHub)
code-coveragecomposercontinuous-integrationgithub-actionsphpphp-extensionsstatic-analysistools
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/setup-php)Questions
- Does setup-php run?
- setup-php runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test setup-php?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f3d967b8bc6d. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test setup-php?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does setup-php take to install?
- 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 setup-php need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing setup-php?
- 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 setup-php?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.