Hi Simon, I couldn't reproduce the issue today. Here are my test results:
GPII/windows commit: df46eb3890959b96e4a8b9dc05b7978e0d348c99 GPII/universal commit: 8f84cf12d40ce0a29e94e88ba9db4840e616b3d4 (GPII-2662, Jan 2018) vagrant up status: success vagrant up time #1: 15m34s vagrant up time #2: 17m37s GPII/windows commit: df46eb3890959b96e4a8b9dc05b7978e0d348c99 GPII/universal commit: ac13bc5e2058c87e2860dfd080bd9822d563f6c2 (GPII-2738, Dec 2017) vagrant up status: success vagrant up time: 16m13s GPII/windows commit: df46eb3890959b96e4a8b9dc05b7978e0d348c99 GPII/universal commit: 694422fc218ed6fdb31278242e67cf2fec8b8901 (GPII-2583, Oct 2017) vagrant up status: success vagrant up time: 20m38s Environment was a CentOS 7.4 host, VirtualBox 5.2.6 and vagrant 2.0.1, located in OCAD's datacenter. Yesterday, OCAD's upstream network provider (Cogent) was having some issues. Cloning GPII/windows was happening at 56KB/s. Today the issue with Cogent seems resolved. I just cloned GPII/windows at 10MB/s. Yesterday's packet loss: Start: Wed Jan 31 20:59:59 2018 HOST: h-0005.tor1.inclusivedesign.ca Loss% Snt Last Avg Best Wrst StDev 1.|-- gateway 0.0% 60 0.2 0.2 0.1 0.3 0.0 2.|-- 205.211.169.3 0.0% 60 0.6 0.6 0.4 0.8 0.0 3.|-- 205.211.168.4 0.0% 60 0.7 0.9 0.6 4.9 0.6 4.|-- gi0-0-1-17.210.nr11.b011027-0.yyz02.atlas.cogentco.com 16.7% 60 11.4 14.3 6.8 45.2 9.1 5.|-- 154.24.42.65 16.7% 60 9.9 16.2 7.9 44.0 9.7 6.|-- te0-0-0-9.ccr31.yyz02.atlas.cogentco.com 6.7% 60 6.1 13.2 6.1 47.4 8.5 7.|-- level3.yyz02.atlas.cogentco.com 15.0% 60 9.8 14.8 5.5 62.5 10.4 8.|-- ae-2-4.bear2.Washington111.Level3.net 95.0% 60 27.6 27.8 27.6 28.1 0.0 9.|-- GITHUB-INC.bear2.Washington111.Level3.net 21.7% 60 25.3 31.2 24.4 65.2 9.6 10.|-- ??? 100.0 60 0.0 0.0 0.0 0.0 0.0 11.|-- ??? 100.0 60 0.0 0.0 0.0 0.0 0.0 12.|-- lb-192-30-253-112-iad.github.com 18.3% 60 31.9 31.8 24.0 80.8 12.2 <=== Today's packet loss: Start: Thu Feb 1 09:50:57 2018 HOST: h-0005.tor1.inclusivedesign.ca Loss% Snt Last Avg Best Wrst StDev 1.|-- gateway 0.0% 60 0.3 0.2 0.1 0.3 0.0 2.|-- 205.211.169.3 0.0% 60 0.6 0.8 0.4 9.2 1.2 3.|-- 205.211.168.4 0.0% 60 0.8 0.9 0.5 8.0 0.9 4.|-- gi0-0-1-17.210.nr11.b011027-0.yyz02.atlas.cogentco.com 0.0% 60 1.4 1.3 1.0 3.6 0.3 5.|-- 154.24.42.65 0.0% 60 1.1 1.2 0.9 2.0 0.0 6.|-- te0-0-0-9.ccr31.yyz02.atlas.cogentco.com 0.0% 60 0.9 0.9 0.7 1.3 0.0 7.|-- level3.yyz02.atlas.cogentco.com 0.0% 60 1.0 1.5 1.0 24.2 2.9 8.|-- ae-2-4.bear2.Washington111.Level3.net 85.0% 60 18.2 18.2 18.1 18.4 0.0 9.|-- GITHUB-INC.bear2.Washington111.Level3.net 0.0% 60 18.4 18.4 18.0 25.3 0.9 10.|-- ??? 100.0 60 0.0 0.0 0.0 0.0 0.0 11.|-- ??? 100.0 60 0.0 0.0 0.0 0.0 0.0 12.|-- lb-192-30-253-112-iad.github.com 0.0% 60 18.2 18.1 18.0 18.3 0.0 <=== It's hard to say without having error logs but yesterday's issues could be network related (since the provisioning process downloads a lot of software that doesn't come pre-installed in the Win10 box). I only tested access to GitHub but it's likely that downloading packages from Chocolatey was also affected. Best regards, Giovanni _______________________________________________ Architecture mailing list [email protected] https://lists.gpii.net/mailman/listinfo/architecture
