Skip to content
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

CI: Move AppVeyor to Miniconda instead of native Python installations #696

Closed
wants to merge 5 commits into from

Conversation

effigies
Copy link
Member

Fixes #665.

Closes #676.
Closes #680.

@coveralls
Copy link

coveralls commented Nov 27, 2018

Coverage Status

Coverage remained the same at 91.824% when pulling 3617a72 on effigies:ci/appveyor_miniconda into a13de6e on nipy:master.

@effigies effigies force-pushed the ci/appveyor_miniconda branch from dd5cfcd to 3205167 Compare January 1, 2019 20:48
@codecov-io
Copy link

codecov-io commented Jan 1, 2019

Codecov Report

Merging #696 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #696   +/-   ##
=======================================
  Coverage   88.83%   88.83%           
=======================================
  Files          93       93           
  Lines       11460    11460           
  Branches     1896     1896           
=======================================
  Hits        10181    10181           
  Misses        937      937           
  Partials      342      342

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a13de6e...3617a72. Read the comment docs.

@effigies
Copy link
Member Author

This effort is dead. The bug seems to be happening less lately, so hopefully whatever was going on over at AppVeyor is resolved. I think if this recurs, we should think about moving to Azure Pipelines for Windows tests.

@effigies effigies closed this May 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[WIN] Stochastic bug: Minc2 data may load as np.longdouble in h5py < 2.10
3 participants