This repository was archived by the owner on Dec 6, 2023. It is now read-only.
[MRG] Continuous integration on Python 3.6 - #118
Closed
vene wants to merge 3 commits into
Closed
Conversation
vene
changed the title
vene
commented
Jun 10, 2017
| language: python | ||
| python: | ||
| - "2.7" | ||
| - "3.4" |
Contributor
Author
|
we do not seem to need conda-build in appveyor.yml The 64-bit py36 failure in the debiasing test seems genuine and very, very weird. (see #117) |
Member
|
Feel free to remove conda-build, it probably comes from the time (pre conda-forge) where I used this to build the conda package |
Contributor
Author
|
it would be nice to figure out the reason for the weird failure and fix it... I'm clueless |
Contributor
|
With merged #161 this PR can be closed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
In appveyor I am a bit confused because the PYTHON env var seems to point to "system" python while MINICONDA points to a conda-installed python, and these are different in the provided build environment, as shown here. Let's see if this works right.