-
Notifications
You must be signed in to change notification settings - Fork 27
Test that an actor cannot Abort with a system exit code #15
Comments
Since all built-in actors are presumed to behave correctly and not violate this rule, I suspect we will need to implement a custom actor type and register it via Assigning to me for now, because this requires further investigation, and likely batching all these behaviours known to be illegal (and therefore never found in practice) into a single "Mischievous Actor" custom type (like the Puppet actor is another custom type for testing). |
Yes, I think the Puppet Actor or something like it is the best approach. |
@anorth either I have written broken tests, or our assumptions are wrong: An actor aborting with exitcode in I marked you on the PR just in case. |
😱 . Don't assume the implementation is correct! |
Test that if an actor calls Abortf with an ExitCode within the range [0, 15] the runtime should abort with SysErrorIllegalActor.
Test also that a negative value also results in SysErrorIllegalActor
The text was updated successfully, but these errors were encountered: