-
Notifications
You must be signed in to change notification settings - Fork 85
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
Miniconda34-x64 failing with raise ValueError(str(list(result.keys()))) #157
Comments
You forgot to include the error itself:
|
Regardless of the error, set |
The error means that the output of You need to get this output yourself to find out what is wrong with it. Calling |
Ah - maybe you need this incantation?
E.g. : https://github.com/MacPython/nipy-wheels/blob/master/appveyor.yml#L39 |
Test using https://ci.appveyor.com/project/biopython/biopython-wheels/build/1.0.55 Again this target failed: https://ci.appveyor.com/project/biopython/biopython-wheels/build/1.0.55/job/qrkc6ua4k63jlptk Not sure this tells me anything helpful:
I'll try Matthew's suggestion next... |
That seems to be what I was missing, well spotted @matthew-brett - thank you! https://ci.appveyor.com/project/biopython/biopython-wheels/build/1.0.56 Also I note that this seems not to cause any problems with 32bit targets, so does not need wrapping in an if-statement. |
This seems to be harmless for the 32bit targets. Tested on branch, this should resolve #3 See https://github.com/matthew-brett/multibuild/issues/157
It took a couple of tweaks to refresh the multibuild configuration for our repository https://github.com/biopython/biopython-wheels/ but I was able to build all our Mac and Linux wheels using TravisCI, and almost all the Windows wheels.
Our current
appveyor.yml
file,https://github.com/biopython/biopython-wheels/blob/77b948054f4207cec563e922781f93054f82745d/appveyor.yml
This single target is failing:
https://ci.appveyor.com/project/biopython/biopython-wheels/build/1.0.54/job/86t1cjvxigjqodv4
(Updated to include final two lines which I missed in initial copy-and-paste)
Any thoughts on what might be breaking on this specific platform (64-bit Python 3.4)?
I consider this low priority as most of our Windows users are likely to want a more recent Python.
The text was updated successfully, but these errors were encountered: