tree 38573c8642b9ee8ff6e478ec1294c8451c692ae7
parent f0ba189a9d1b61e25fe64750132bc1009d906d8a
author Xinhao Yuan <xinhaoyuan@google.com> 1754358046 -0700
committer Copybara-Service <copybara-worker@google.com> 1754358097 -0700

Abort on external failures in runner mode instead of keep running.

This mainly affects the unit-test mode behavior when dealing with gtest assertion failures.

This is to prepare for persistent mode, where multiple batches run in a single runner process (inside RunnerMain()).
Aborting after failure input ensures Centipede know which batch contains the failure and triage accordingly.

As a side-effect, change a unit-mode e2e test to switch to a non-failing test because the previous test generates an external failure (gTest EXPECT failure) which would cause the runner to abort without destructing the global environment.

PiperOrigin-RevId: 790977540