Fix flaky signal tests.
The signal tests that send a SIGUSR1 signal to a remote process, can lead to a case where the code winds up in a location for which the unwind information is not 100% accurate. This happens near the end of the atomic functions which manipulate the stack right before returning, but do not have separate cfi instructions for those last few instructions. Add a new test type for the from_context test that will wait explicitly for the global g_finish and not piggy back on the remote test type. Bug: 122902885 Test: Ran flaky tests 1000 times without failure on a taimen. Change-Id: I7d0c9b016e3a3a2c0c0949cf74af11d7785a008c
Loading
Please register or sign in to comment