|
|
cloud9's build is used from other build.zig files (pardes, sketchbook),
and nothing in its own suite used it that way: a break in what a
consumer writes was found by the consumer. test/consumer is a package
of its own whose manifest names cloud9 by ../.. and whose build.zig
takes both exported modules by name with no option,
b.dependency("cloud9", .{}).module("cloud9") and .module("9proc"),
for its own target and optimize. Its test is a client and a server,
each a cloud9 session (Client, Server) on its own end of a Unix socket
pair, through a version, an attach and a read; and a call into 9proc,
which shares the consumer's cloud9 module. The library's test step runs
it as a nested zig build test in test/consumer, as pardes's lib-test
runs test/lib (the consumer depends back on cloud9, so it cannot be a
dependency of it). It has its own .zig-cache there (39 MB after a run).
build.zig.zon's paths already carry test/ and every directory build.zig
imports, so a fetched copy builds as before: unchanged.
zig build test: the library's 108 of 108 and test/consumer's 2 of 2 at
load 3.6 (at load 14, 107: serve's "repeated connect/disconnect", which
fails on the base under load too, from the same test binary); a warm
zig build test, the nested one included, 42-50 ms. 9proc-test and
9proc-check-freestanding pass: 9proc's library test binary is the
base's (one cache key), so the first change's copy of the module is the
module it was.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_016Y9MNBECMWcJD5pdS4SR6T
|