From the latest reliability report, it seems many of the SEA tests are running into SIGSEGV on Windows/macOS/RHEL when executing the generated SEA.

nodejs/reliability#718

Some ideas about investigating into the flakes:

1. Use spawnSyncAndExitWithoutError() for better output
2. Use NODE_DEBUG_NATIVE=SEA to log the deserialization
3. Log onto the machines to check out what's going on

cc @nodejs/single-executable