tree 946778edbc160b0c3ed9df33e877caaa69f26b39
parent da7d0e60dd28ede70f80b18c20d9658ebf8a0f76
author Chris Masone <cmasone@google.com> 1751324703 -0700
committer Chris Masone <cmasone@google.com> 1751410932 -0700

[mobly] Exit non-zero on signals.TestAbortAll

Per https://github.com/google/mobly/issues/960 Mobly incorrectly exits
either 0 or 1 when a test raises signals.TestAbortAll -- depending on
whether any previous tests have failed or not. Instead of exiting 1 in
the case of all tests being aborted, like any other failure, exit with
a special code.

There aren't a lot of standard codes in use, but some internal google
docs suggest 40 for generic retryable errors. So use that.

Bug: b/425675837
Change-Id: Iae58f6c896df2cc3d93ca9c51a84513dcd82db34
Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/github.com/google/mobly/+/1312367
Reviewed-by: Prashanth Swaminathan <prashanthsw@google.com>