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
..
2024-12-19 17:10:03 -05:00
2025-01-16 20:42:08 -05:00
2024-02-23 02:37:11 -07:00
2025-01-16 20:42:08 -05:00
2024-07-23 11:43:12 -07:00
2025-01-16 20:42:08 -05:00
2024-07-09 14:25:42 -07:00
2024-03-10 18:13:30 -07:00
2025-01-16 20:47:30 -05:00
2024-08-22 08:44:08 +02:00
2024-03-21 14:11:46 -07:00
2024-11-01 02:04:27 +03:30
2025-01-16 20:42:08 -05:00
2024-08-07 00:48:32 -07:00
2024-07-31 16:57:42 -07:00
2025-01-16 20:42:08 -05:00
2024-07-19 00:30:32 -07:00
2025-01-16 20:42:08 -05:00
2024-08-29 23:43:52 +01:00
2025-01-16 20:42:08 -05:00
2024-07-09 14:25:42 -07:00
2025-01-16 20:42:08 -05:00