tree 57b8eed42c3a8fa12417b3dfbdc85e0938e7158d
parent 3c3b1ec9b355fcffc3fc00617bbbfb14eecc7c95
author Ian (Hee) Cha <heec@google.com> 1689270794 -0700
committer GitHub <noreply@github.com> 1689270794 +0200
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJksDoKCRBK7hj4Ov3rIwAAlosIAAXgIRGmkcoes7ZwL+6Jw6/5
 i+Ye7l8/vZccE7Zh8oUuP+MmqEbPBB0se70jNPoLsj6dYxw6tahgPJ2SnWaFaxUX
 nCqLX1mT861eQ4gC6WmQkSs3Mn9DioHeD+Ma/BK2KJn9Hjs2RJo1FFFhtbf75yky
 yYvxnCbC4zzdHji6LGGv6KVepq3Bl18/1evPE/Mul+LXRGr/fYID7qYtU09Etfii
 LfOefP+PBEIOMbD9OOOBcpm8rbPB1KxJBo2G5Lk3h7xMIo34Ga0hhSOKkNxXXF7z
 uh1y2qNU7hKoZRyanxsK5k5XgTYVIQ2+PfHfykmS8jS7+v2EhOelBV2BD3TMU5Y=
 =GpnT
 -----END PGP SIGNATURE-----
 

test-setup.sh: Attempt to raise the original signal once more (#18932)

On POSIX-like systems, processes may either terminate normally with an integer exit code. The exit code may span the full range of int, even though all but the waitid() function retur the bottom eight bits. In addition to that, processes may terminate abnormally due to a signal (SIGABRT, SIGSEGV, etc.)

POSIX shells (sh, bash, etc.) are more restrictive, in that they can only return exit codes between 0 and 126. 127 is used to denote that the executable cannot be found. Exit codes above 128 indicate that the process terminated due to a signal.

Right now we let test-setup.sh terminate using the exit code obtained using $?. This means that if a program terminates due to SIGABRT, test-setup.sh terminates with exit code 128+6=134. This causes us to lose some information, as the (remote) execution environment now only sees plain exit codes.

This change extends test-setup.sh to check for exit codes above 128. In that case it will send a signal to itself, so that the original signal condition is raised once again.

See also: https://github.com/bazelbuild/remote-apis/issues/240

Closes #18827.

PiperOrigin-RevId: 547773406
Change-Id: Ia29a6ea1eefdb8caa5624a799755b420a61478a0

Co-authored-by: Ed Schouten <eschouten@apple.com>