| commit | b542daf156fd2ca07b838d2d702a61e372ec6113 | |
| author | Eric Bluestein <ericblue@fb.com> | |
| Thu, 18 Jan 2018 05:38:44 +0000 (17 21:38 -0800) | ||
| committer | Hhvm Bot <hhvm-bot@users.noreply.github.com> | |
| Thu, 18 Jan 2018 05:48:07 +0000 (17 21:48 -0800) | ||
| tree | 95ebe268db9f25ce98e4040ab714145b0cbe1116 | treesnapshot (tar.gz zip) |
| parent | 98b4582be4b6eac54dc26afe4332fb21ef932bf8 | commitdiff |
Nuclide HHVM Debugger - Fix flaky test shutdown
Summary: When the HHVM process finishes running a script, it can exit without flushing the remaining VS debug protocol messages into the TCP socket. The real client doesn't care so much when this happens, since the debug wrapper terminates the debug session if it sees the TCP socket close. The tests should be resiliant to this as well.
Reviewed By: vladima
Differential Revision: D6733753
fbshipit-source-id: cbf87d46c37a4a1404f8ddf87d8087e180bffadc
Summary: When the HHVM process finishes running a script, it can exit without flushing the remaining VS debug protocol messages into the TCP socket. The real client doesn't care so much when this happens, since the debug wrapper terminates the debug session if it sees the TCP socket close. The tests should be resiliant to this as well.
Reviewed By: vladima
Differential Revision: D6733753
fbshipit-source-id: cbf87d46c37a4a1404f8ddf87d8087e180bffadc