Remove some raciness from the TestProcessAttach.test_run_then_attach_wait_interrupt
command. We were reading the command output right after sending the interrupt, but sometimes that wasn't long enough for the command result text to have been emitted. I added a poll for the state change to eStateExited, and then added a bit more sleep to give the command a chance to complete.
parent
77053421
Please register or sign in to comment