mlugg b8e568504e std.Build: extend test_runner option to specify whether runner uses std.zig.Server ... The previous logic here was trying to assume that custom test runners never used `std.zig.Server` to communicate with the build runner; however, it was flawed, because modifying the `test_runner` field on `Step.Compile` would not update this flag. That might have been intentional (allowing a way for the user to specify a custom test runner which *does* use the compiler server protocol), but if so, it was a flawed API, since it was too easy to update one field without updating the other. Instead, bundle these two pieces of state into a new type `std.Build.Step.Compile.TestRunner`. When passing a custom test runner, you are now *provided* to specify whether it is a "simple" runner, or whether it uses the compiler server protocol. This is a breaking change, but is unlikely to affect many people, since custom test runners are seldom used in the wild.		2025-01-20 00:14:58 +00:00
..
build.zig	std.Build: extend test_runner option to specify whether runner uses std.zig.Server	2025-01-20 00:14:58 +00:00
test.zig	test: add test_runner_path test	2022-11-02 22:41:20 +11:00
test_runner.zig	re-enable standalone tests based on build.zig	2023-03-15 10:48:14 -07:00