Plugin eval runs now handle kill signals with proper exit codes and title reports with plugin names.
What's wrong with this entry?
The plugin eval runner now traps SIGTERM as well as SIGINT, exiting 143 and 130 respectively, and records the run outcome as "terminated", "interrupted" or "signal_killed". Report titles now name the suite's plugins and versions instead of the fixed heading "Eval suite".
- An interactive interview killed by a signal reports an exit code computed as 128 plus the signal number.
- Every stderr line is passed through a control-character stripper before being shown.
Eval suite
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.235
plugin evalnow tells you when a nearby plugin is not being loadedBoth mention eval
-
v2.1.235
--eval-diron the eval command, with warnings that name the fixBoth mention eval
-
v2.1.235
Eval setup refuses directories it cannot vouch for
Both mention eval