-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
build: windows stage0.exe should loop, try harder #10071
Comments
Also, the buildlet should maybe not log for every file written on Windows. It almost looks like we're being limited by the speed of the console (cmd.exe). We should benchmark and verify. |
I started looking into this. One of the first things Maybe we should loop waiting for the network to come up before doing On 4 March 2015 at 08:44, Brad Fitzpatrick notifications@github.com wrote:
|
shell out to 'ipconfig' perhaps?
|
On 5 March 2015 at 17:56, Minux Ma notifications@github.com wrote:
stage0 should work on all machines. |
I googled. You can do something like that http://www.winvistatips.com/threads/always-wait-for-network-at-computer-startup-and-logon.720146/ To run "Group Policy Editor" just run gpedit.msc. But I think your proposal to try and connect to something on the Internet sounds good to me. Alex |
I think I figured out why the Windows VMs don't always come up into a buildlet.
I just saw "gomote create" of a Windows VM failed, so I connected to it fine with RDP. It booted, but the stage0.exe was gone. It must've failed and died. I don't know why, but maybe networking wasn't fully up yet? It should loop a few times with a sleep.
Then we should rebuild the Windows image too with a 40 GB base instead of a 100 GB base. (since we'll have to rebuild anyway to update stage0, and 40 GB is now available I hear, whereas only 100 GB was available before)
/cc @adg
The text was updated successfully, but these errors were encountered: