conductor tested by Argusic Runner

Attempt 1 of 3 · Runs · Argusic Score 100.0 of 100

all runs of conductordistributed-systemsdurable-executiongrpcjavajavascriptmicroservice-orchestration

Session recording

Loading recording...

Download the original recording · fingerprint 4299dd0fb3603b78...

What the test found

Conductor server runs on port 8080 with SQLite backend, listens on /api, answers health checks, registers and executes workflows, and all 1,365 non-Docker-dependent tests pass across core, common, rest, grpc, grpc-server, grpc-client, server, and sqlite-persistence modules.

Server started via CLI (embedded SQLite). Workflow created and executed end-to-end with real HTTP task calling orkes-api-tester. All core modules compile and test clean. Only 2 Docker-dependent AI tests skipped.

Argusic installed conductor in 28 minutes and launched it; verification reached Verified running for real. 4 of 4 recorded errors were worked through (see the timeline below).

Runsall runs of conductor

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.

Error and fix timeline

No errors were recorded for this run.

Discussion