arroyo
Distributed stream processing engine in Rust
Not yet verifiedsource: GitHubhomepageRustApache-2.0commit 0630bece757a
Rust, Apache-2.0 licensed. The project labels itself: data, data stream processing, dev tools, infrastructure, kafka, rust, sql and stream processing.
arroyo has not been verified yet.
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 20 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 most recent recorded attempt, which did not reach a verdict. Every line is a recorded value, not an estimate.
- Cold machine to finish
- 50 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- Model tokens used
- 174,888
- Exact commit tested
- 0630bece757a
- 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.
- Install time
- the run did not report one
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
warning: build failed, waiting for other jobs to finish... exec /bin/sh -lc "export CC=gcc CXX=g++ && \\ export PATH=\""'$HOME/.local/bin:$HOME/.local/share/pnpm:$HOME/.cargo/bin:$PATH" && '"\\ export LIBCLANG_PATH=\"/tmp/clang17/clang+llvm-17.0.6-x86_64-linux-gnu-ubuntu-22.04/lib\" && \\ export LD_LIBRARY_PATH=\"/tmp/clang17/clang+llvm-17.0.6-x86_64-linux-gnu-ubuntu-22.04/lib:"'$LD_LIB… export BINDGEN_EXTRA_CLANG_ARGS=\"-isystem /usr/lib/gcc/x86_64-linux-gnu/13/include -isystem /usr/l… cd /work/repo && cargo build --package arroyo 2>&1 | tail -30" in /work/repo 2026-09-29T23:05:49.066993Z ERROR codex_core::session: failed to record rollout items: thread 01a0e… tokens used 174,888 LLVM 17 links against `libtinfo.so.6` which is available. Let me try building with that
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.
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 | Did not run | 20.00 | 0.16 |
Topics (from GitHub)
datadata-stream-processingdev-toolsinfrastructurekafkarustsqlstream-processingstream-processing-engine
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/arroyo)Questions
- Does arroyo run?
- arroyo has not been fully verified yet. No recorded run has produced a verdict yet.
- How did Argusic test arroyo?
- On a fresh, disposable machine, with every command recorded. One attempt is recorded, and the full method is on the methodology page.
- Where is the evidence for arroyo?
- 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.