ReplSignalRunResult
What one run under a ReplProcessSignalHarness ended with.
- Kind:
Class - Namespace: Repl.Testing
- Assembly:
Repl.Testing - Source: src/Repl.Testing/ReplSignalRunResult.cs
Signature
Section titled “Signature”public sealed record ReplSignalRunResult : IEquatable<ReplSignalRunResult>Inheritance
Section titled “Inheritance”Implements
Section titled “Implements”IEquatable<ReplSignalRunResult>
Properties
Section titled “Properties”DiagnosticText
Section titled “DiagnosticText”Everything the run wrote to its error stream. That includes the framework diagnostics raised while the run itself was running: a signal bridge that could not be installed, and a cancellation callback that threw while the run was unwinding.
It does not include the diagnostics for delivered signals. Those are written from whichever context delivers the signal — an operating-system callback thread in production, with no session of its own — so they belong to the delivery and are captured on DiagnosticText instead.
public required string DiagnosticText { get; init; }Returns
Section titled “Returns”ExitCode
Section titled “ExitCode”The status the run resolved to, through the application’s own ExitCodes
policy. This is what a real Main would return; the harness does not exit the process, so
nothing acts on it here.
public required int ExitCode { get; init; }Returns
Section titled “Returns”OutcomeKind
Section titled “OutcomeKind”How the run ended. A claimed signal reports Interrupted; a run cancelled by its own caller token reports Cancelled.
public required ReplExecutionOutcomeKind OutcomeKind { get; init; }Returns
Section titled “Returns”OutputText
Section titled “OutputText”Everything the run wrote to its output.
public required string OutputText { get; init; }