Skip to content

Conda channels are in wrong order in Windows Tests on Azure #28356

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

Closed
xhochy opened this issue Sep 9, 2019 · 0 comments · Fixed by #28357
Closed

Conda channels are in wrong order in Windows Tests on Azure #28356

xhochy opened this issue Sep 9, 2019 · 0 comments · Fixed by #28357
Labels
CI Continuous Integration Windows Windows OS
Milestone

Comments

@xhochy
Copy link
Contributor

xhochy commented Sep 9, 2019

We currently have

channels:
- defaults
- conda-forge
for the requirements in the Windows tests. This is sadly a known source for problems as there are conflicting packages in both channels, e.g. boost from defaults and conda-forge is in different packages (libboost vs boost-cpp) and thus both can be installed while one is overriding the other (for boost this is fixed but there are several other packages). See also https://conda-forge.org/docs/user/tipsandtricks.html#multiple-channels for another explanation. The wrong order is probably a source of issues like #23180

@gfyoung gfyoung added CI Continuous Integration Windows Windows OS labels Sep 9, 2019
@jorisvandenbossche jorisvandenbossche added this to the 1.0 milestone Sep 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous Integration Windows Windows OS
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants