Paul Hinze 1e84cc4d6a communicators/winrm: respect boot_timeout when fetching winrm_info ... We gained a ton of improvemnts to WinRM error handling in https://github.com/mitchellh/vagrant/pull/4943, but we also got one bug. The new code raises an exception when `winrm_info` does not return right away. This was preventing us from catching the retry/timout logic that's meant to wait until boot_timeout for the WinRM communicator to be ready. This restores the proper behavior by rescuing the WinRMNotReady exception and continuing to retry until the surrounding timeout fires.		2015-09-02 16:36:23 -05:00
..
command_filters	Remove unneeded executable permissions.	2015-01-20 11:53:30 +01:00
scripts	Fix issue 5790	2015-06-10 16:04:46 -07:00
command_filter.rb	Added mkdir command filter for WinRM to be compatible with PS4+	2014-07-30 15:43:11 -04:00
communicator.rb	communicators/winrm: respect boot_timeout when fetching winrm_info	2015-09-02 16:36:23 -05:00
config.rb	Add retry_delay setting to speed up test	2015-01-28 13:41:07 -05:00
errors.rb	Better error handling for WinRM (using winrm v1.3.0.dev.2)	2014-12-11 13:22:39 -05:00
helper.rb	communicators/winrm: use winrm_info cap if available [GH-3832]	2014-05-20 20:13:36 -07:00
plugin.rb	communicators/winrm: silence warnings loading winrm	2014-04-21 13:51:27 -07:00
shell.rb	Raise Errno::ETIMEDOUT as "acceptable" Errors::ConnectionTimeout	2015-07-15 19:41:10 +02:00