You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@tcr So, after some testing, it seems that original race conditions no longer exist between issuing the setup commands to the virtual machine and the shutdown.
On occasion I am still getting an error where our 10 second wait built in here is not long enough to insure that the vm has started before we open the socket.
I think instead a more robust solution may be to employ the vboxmanage list runningvms command instead of our hard 10 second wait.
example output:
C:\dev\npm-modules\t2-vm>vboxmanage list runningvms
"tessel2" {3c9d6884-6816-4a50-b4cd-0e0f3f2d43ea}
See #11. Check out branch https://github.com/tessel/t2-vm/tree/ondreian-patches for race condition patches. /cc @ondreian
The text was updated successfully, but these errors were encountered: