Fix autoupdater tests on TLS-fragile platforms #2344
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problems
We have three failing tests currently. (Travis skips them by excluding anything tagged with FlakyNetwork, which these are.)
Causes
We need to set
ServicePointManager.SecurityProtocol
before accessing GitHub to enable TLS1.2, see #2297. Running tests bypasses that.After you fix these three, another test failure happens:
This happens because we stop searching a release for
ckan.exe
after we findAutoUpdater.exe
due to an errantbreak
statement. I think this means the auto-updater in 1.24.0 won't work.Changes
ServicePointManager.SecurityProtocol
is set before network accesses in the affected tests.The
break
statement is removed to makeFetchLatestReleaseInfo
continue through all the needed assets.After these changes, all tests now pass.