turbo

Turbo is a light-weight flow engine framework, support BPMN2.0. 一款轻量级流程引擎服务框架,可作为底层服务支持各类流程设计、低代码设计、工作流、审批流、服务编排等场景

Runssource: GitHubJavaApache-2.0commit 4cac6b00af0f

Java, Apache-2.0 licensed. The project labels itself: bpmn, flow engine, java, low code, lowcode and workflow.

turbo runs. An Argusic agent installed it in 15 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Turbo builds and compiles successfully with JDK 21 + Maven 3.9.9. Engine module 93/93 tests pass using H2 in-memory database. Demo module 11/11 tests pass using H2, exercising full flow lifecycle (create, deploy, save, query, parallel gateway, inclusive gateway, commit, rollback). Parallel-plugin 7/7 DAO tests pass; 3/9 RuntimeProcessorTest fail due to pre-existing test isolation issue with shared H2 state.

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 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.30 (measured)
recorded runs
2
last tested
stars
1,223
forks
232
open issues
45
watchers
32
size
3 MB
created
last push

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.

Time lost to each failure while testing turbo, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Engine tests configured for MySQL but MySQL is not running2 minutes
  • Parallel-plugin tests configured for MySQL - same issue2 minutes
  • No JDK available in container - java not found1 minute
  • No Maven available in container - mvn not found0.5 minutes
  • JUnit version conflict between vintage 5.10.2 and platform 1.12.20.5 minutes
  • Abstract BaseTest class detected as runnable test0.5 minutes
Install time
15 minutes
Cold machine to finish
23 minutes
Errors hit and fixed
7 hit, 7 fixed with no human help
How the result was proved
mvn test -pl engine,demo: 93 engine tests passed (dao, mapper, processor, executor, validator) + 11 demo tests passed (FlowControllerTest=5, ParallelGatewayDemoTest=4, DemoTest=2). BUILD SUCCESS. Parallel-plugin DAO handler tests (7/7) pass. 3/9 RuntimeProcessorTest fail only when run in batch due to H2 shared state.
Model tokens used
278,048
Exact commit tested
4cac6b00af0f
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.

Try 'tail --help' for more information.
could not sum
exec
/bin/sh -lc 'echo "Started around $(date -d @1794976069 2>/dev/null || echo '"'04:27:49')\" && echo…
 succeeded in 0ms:
Started around Wed Nov 18 04:27:49 UTC 2026
Now Wed Nov 18 04:49:21 UTC 2026
Minute estimate: ~15 min
Now I have everything I need for the final report.
tokens used
278,048
Now I have everything I need for the final report.

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 15 minutes.
  • Recovered from all 7 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 Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.30
Argusic Runner1/3Runs with mocks92.000.16

Topics (from GitHub)

bpmnflow-enginejavalow-codelowcodeworkflow

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/turbo.svg)](https://argusic.com/subject/turbo)

Questions

Does turbo run?
Yes. turbo runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 7 errors on the way, and recorded the session.
How did Argusic test turbo?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4cac6b00af0f. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test turbo?
The run that produced this verdict cost $0.30: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does turbo take to install?
15 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 turbo need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing turbo?
7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for turbo?
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.

Discussion