8b7db1382d
This solves two problems: * xharness thinks it crashed if the exit code is neither 0 nor 1, and helpfully says so and tries to collect crash reports, which only ends up being confusing. * The exit code is byte-sized on macOS. This means that trying to return 256 actually returns 0 (success). |
||
---|---|---|
.. | ||
Reporter.cs | ||
xtro-report.csproj |