concourse
Concourse is a container-based automation system written in Go. It's mostly used for CI/CD.
Runs with mockssource: GitHubhomepageGoApache-2.0commit d6e25a33812a
Go, Apache-2.0 licensed. The project labels itself: ci, ci cd, concourse, containerd, containers, continuous delivery, continuous integration and elm.
concourse runs, with stand-ins for the services it depends on. An Argusic agent installed it in 45 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Concourse binary builds and runs, Go test suites across atc/cmd/fly/skymarshal/tsa/worker packages all pass (except baggageclaim driver tests needing kernel features), Elm source compiles and 509 unit tests verified passing, CSS builds via lessc, npm dependencies installed via yarn.
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.
- Elm test suite (3095 tests) spawns 192 parallel workers (equal to CPU count), causing socket IPC failures20 minutes
- initdb/postgres binaries not available for test suite3 minutes
- Go compiler not pre-installed2 minutes
- yarn not pre-installed and npm install -g blocked by permissions2 minutes
- Postgres JIT loader fails with missing libLLVM-17.so.11 minute
- Install time
- 45 minutes
- Cold machine to finish
- 81 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- go test ./atc/... passed all suites (45+ sub-packages); go test ./cmd/concourse passed 10/10 specs; go test ./fly/... passed all suites; go test ./tsa/... passed; go test ./skymarshal/... passed all suites; elm-test on 5 major test files passed 509/509 tests; elm make src/Main.elm succeeded; concourse binary built and reports version 0.0.0-dev
- Model tokens used
- 445,370
- Exact commit tested
- d6e25a33812a
- 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.
2026-09-28T06:19:45.669694Z ERROR codex_core::session: failed to record rollout items: thread 01a0e… tokens used 445,370 Now I have enough data to produce the final report. Let me compile it. **Time spent**: ~45 minutes from start to the latest test results. **Summary of what was done:** - Installed Go (downloaded), yarn (extracted from npm pack), PostgreSQL (extracted from Ubuntu debs… - Patched `atc/postgresrunner/postgresrunner.go` to disable JIT (fixes missing LLVM library in extr… - Built the `concourse` binary - Ran Go test suites across ~30+ packages - Ran Elm tests for verified subsets (509 tests confirmed passing) - The full Elm test suite (3095 tests) can't run due to elm-test's worker-per-CPU approach with 192…
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 45 minutes.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, 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.44 |
Topics (from GitHub)
cici-cdconcoursecontainerdcontainerscontinuous-deliverycontinuous-integrationelmgopipelinesrunc
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/concourse)Questions
- Does concourse run?
- concourse runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 45 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test concourse?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d6e25a33812a. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test concourse?
- 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 concourse take to install?
- 45 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 concourse need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing concourse?
- 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.
- Where is the evidence for concourse?
- 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.