Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine if race conditions still exist on Windows. #13

Open
tcr opened this issue Jun 3, 2015 · 2 comments
Open

Determine if race conditions still exist on Windows. #13

tcr opened this issue Jun 3, 2015 · 2 comments

Comments

@tcr
Copy link
Member

tcr commented Jun 3, 2015

See #11. Check out branch https://github.com/tessel/t2-vm/tree/ondreian-patches for race condition patches. /cc @ondreian

@ondreian
Copy link
Contributor

ondreian commented Jun 9, 2015

@tcr Just a quick update, I'm back from my travels and my schedule is looking like I won't be able to get to this until tomorrow or the next day.

@ondreian
Copy link
Contributor

@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}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants