-
-
Notifications
You must be signed in to change notification settings - Fork 384
Travis build broken #352
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
Comments
@tpaviot No, I have no clue. Our conda packages are also unchanged for more than a month now. It must be some conda updates from anaconda that lead to this regression. Look at the dot behind vendor... This looks like the cause of it. |
Similar issue 5 days ago here pypa/pip#4059 |
ok I got it it's an issue with latest pip version on python 2.7. On my windows machine, python2.7, upgrading pip leads to the same problem:
|
It seems it was fixed in a 9.0.1 pip relase published on the 6th of november. The fix is here pypa/pip@d884c30 |
Unfortunately the version 9.0.1 is not available yet in the anaconda channel (still 9.0.0). |
You could also force an older version of pip . |
yep that's what I did see 84b2aec but it does not seem necessary. Indeed pip 9.0.1 is installed on travis, maybe they updated the channel. I triggered another build of master to check if it's ok |
The last successfull build of the master branch is 4 days old. Since that, compilation fails for python2.7 with a curious exception (see https://travis-ci.org/tpaviot/pythonocc-core/jobs/172543060):
It only affects py2.7 and Travis. On appveyor, everything works fine. Hard to say if that comes from Travis or conda. @rainman110 Are you aware of any change on the conda side that coud explain this regression ?
The text was updated successfully, but these errors were encountered: