[lldb/Test] Remove custom tearDownHooks from GDB Remote tests
Remove custom tearDownHooks from GDB Remote tests as we now cleanup subprocesses unconditionally. This also changes the termination order to be the reverse of the creation order. I don't think anything is relying on that right now, but it better fits the setup/teardown paradigm.
Loading
Please sign in to comment