pub const WORKER_STDOUT_READY_PREFIX: &str = "jemalloc-alloc-worker ready";Expand description
Stdout “ready” breadcrumb the ktstr-jemalloc-alloc-worker
binary prints once, immediately before entering its terminal
loop — the default-mode sleep(3600s) park loop or the
--churn spawn+join loop — after its allocation + black_box
triple has materialised.
The full emitted line is
{WORKER_STDOUT_READY_PREFIX} pid={pid} bytes={bytes}; this
const carries only the prefix so host-side consumers that want
to grep the worker’s captured stdout (or that fold worker
stdout into a larger test log) can match against a single
authoritative literal.
Exported as pub const for the same reason as
WORKER_STDERR_PREFIX: a rename or a typo on either side
shows up in one place instead of silently desynchronising the
worker and any test-side assertion. The breadcrumb is
currently not parsed by any automated consumer — readiness is
signalled via the marker file (worker_ready_marker_path),
NOT via stdout — but pinning the literal here means a future
test that wants to correlate “worker log says ready” with
“marker file appeared” has a stable hook.
The trailing space separating the prefix from the
pid= / bytes= tail is NOT part of the constant, matching
the WORKER_STDERR_PREFIX convention.