tableau
Static Site Generator for Elixir
Runssource: GitHubElixirMITcommit 6a6c89430113
Elixir, MIT licensed. The project labels itself: elixir and static site generator.
tableau runs. An Argusic agent installed it in 3.2 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Tableau v0.30.0 compiles, builds, and all 39 tests pass on Erlang/OTP 27.1.1 with Elixir 1.17.3 on Ubunto 24.04
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.
- No Elixir/Erlang runtime in container1.5 minutes
- ncurses-dev headers/libs missing from system0.3 minutes
- Erlang configure: CFLAGS missing -O flag after adding include path0.2 minutes
- libtinfo.so symlink broken in extracted .deb0.1 minutes
- Install time
- 3 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- mix test exited 0, 39 tests passed, 0 failures; mix tableau.build exited 0
- Model tokens used
- 184,304
- Exact commit tested
- 6a6c89430113
- 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.
- Downloaded and extracted `libncurses-dev` from Ubuntu archives (no root for apt) to provide heade… - Built Erlang/OTP 27.1.1 and Elixir 1.17.3 from source via mise (kerl) - Ran `mix deps.get` (24 deps resolved, 0 failures) - Ran `mix compile` (0 warnings, all apps compiled) - Ran `mix test` — 39 tests, 0 failures - Ran `mix tableau.build` — exited successfully **Errors encountered:** 1. No Elixir/Erlang in container — fixed by installing mise and using it to build both tools 2. `ncurses-dev` headers/libs missing at build time — fixed by extracting the `.deb` for `libncurse… 3. Erlang configure failed on missing `-O` flag in CFLAGS after adding the include path — fixed by … 4. `libtinfo.so` was a dangling symlink from the extracted .deb — fixed by creating a symlink to th… **No real credentials were required.** This project has no external service dependencies in its bas…
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 3.2 minutes, faster than the median of the 6 comparable projects Argusic has measured.
- Recovered from all 4 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 7 elixir projects Argusic has installed and timed, tableau was the 1st fastest to reach a running state, and 7 of 7 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.2 minutes after the clone.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/tableau)Questions
- Does tableau run?
- Yes. tableau runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test tableau?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6a6c89430113. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test tableau?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does tableau take to install?
- 3.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 tableau need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing tableau?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does tableau compare with the alternatives?
- Of the 7 elixir projects Argusic has installed and timed, tableau was the 1st fastest to reach a running state, and 7 of 7 reached one at all.
- Where is the evidence for tableau?
- 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.