Repository navigation
Step.Run.setCwd error message is confusing #20793
Description
Zig Version
0.14.0-dev.339+d8f81372f
Steps to Reproduce and Observed Output
- Create an empty folder
- Paste the following code in the
build.zig
const std = @import("std");
pub fn build(b: *std.Build) void {
const call = b.addSystemCommand(&.{
"echo",
"test",
});
call.setCwd(b.path("doesnt-exist"));
b.getInstallStep().dependOn(&call.step);
}- Call
zig build - Observe the following output:
❯❯ zig build
install
└─ run echo failure
error: unable to spawn echo: FileNotFound
Build Summary: 0/2 steps succeeded; 1 failed
install transitive failure
└─ run echo failure
error: the following build command failed with exit code 1:
/home/nightmare/dev/.zig-cache/o/b4517676049306dd7cacdd805efe39a0/build /nix/store/bn3y3ijrvi53w3maxgphczx6np2ngj87-zig-0.14.0-dev.339+d8f81372f/bin/zig /nix/store/bn3y3ijrvi53w3maxgphczx6np2ngj87-zig-0.14.0-dev.339+d8f81372f/lib /home/nightmare/dev /home/nightmare/dev/.zig-cache /home/nightmare/.cache/zig --seed 0x873f8a98 -Z779ae0d26316a393
Expected Output
Something along the lines of:
install
└─ run echo failure
error: unable to setCwd to 'doesnt-exist': IsDirFailed
Activity
prajwalch commentedon Aug 27, 2024
This is due to the fact that there is no proper support for error payloads.
Ferhunt commentedon Jan 13, 2025
My God, this confused me as well. I kept thinking that maybe using setCwd messed up my path or something, but I hadn't realized I was messing up the path to the cwd. Though I'd like error payloads to be added I don't think this is the issue with the error, it's seems like it's just a bug.