Avoid updating Travis conda package manager; issue with conda 4.7.5 dependency graph #898
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.
Travis Miniconda 3.7 affected
While working locally with Anaconda 3.7 on Linux with the latest conda version, 4.7.5, I found that the conda solver ran into this issue with conflicting dependencies, which prevents a solution:
conda/conda#8844
The Travis installation script has been updating the base conda version before installing dependencies.
After I updated .travis.yml on Travis under this PR such that conda is not updated, the version that has been running on Travis is 4.6.14.
Windows is not affected by the issue
I also investigated Miniconda on Windows, and there is apparently not the same problem: a full set of dependencies was determined and installed by conda 4.7.5 for both Miniconda 3.6 and 3.7.
On Appveyor Miniconda 3.7, although conda 4.7.5 is able to solve the dependency graph, there is still an issue with the Appveyor 3.7 configuration such that the build remains inactive.