Skip to content
This repository has been archived by the owner on Oct 17, 2024. It is now read-only.

Remove astropy-ci-extras from the default conda channels #97

Merged
merged 4 commits into from
Jun 15, 2016

Conversation

bsipocz
Copy link
Member

@bsipocz bsipocz commented Jun 15, 2016

This is a workaround for currently failing tests in astropy (e.g. astropy/astropy#5094), a place for discussion for long term solution is in #98.

[Edit] - The PR also manually adds the defaults conda channel, for details see conda/conda#2675

@astrofrog
Copy link
Member

Another solution is to add defaults explicitly - I think we are running into conda/conda#2675

@bsipocz bsipocz merged commit de7cbd6 into astropy:master Jun 15, 2016
@larrybradley
Copy link
Member

The travis-ci tests are still failing for the numpy 1.7 and 1.8 tests because conda is installing astropy 0.3.0 (!) for those tests.

@astrofrog
Copy link
Member

Can we pin the version of conda used?

@bsipocz
Copy link
Member Author

bsipocz commented Jun 15, 2016

what you mean @astrofrog? anaconda doesn't build new versions against old numpies, this the old ones are stucked with the astropy version of the time when they were new.
gitter?

@larrybradley
Copy link
Member

Can conda downgrade itself?

The other option would be if old versions of miniconda are still available for download and then not run conda update conda after installation.

@astrofrog
Copy link
Member

I'm thinking that the issues we are seeing today are a conda bug, so I'm just wondering whether we can revert to an earlier version of conda.

@astrofrog
Copy link
Member

astrofrog commented Jun 15, 2016

By the way, looks like SunPy are having issues too: https://travis-ci.org/sunpy/sunpy/jobs/137763718 - though I've asked @Cadair to restart that to see.

@astrofrog
Copy link
Member

@larrybradley - I think conda can downgrade itself, yes.

@bsipocz
Copy link
Member Author

bsipocz commented Jun 15, 2016

I believe that the conda bug was solved with adding the defaults to the channels. The issue now is coming from the fact that we removed astropy-ci-extras.

This is the list of the available astropy versions on conda:

(astropy-dev)bsipocz@tegla2:~/munka/devel/ci-helpers$ ~/miniconda/bin/conda search astropy|grep np18
Could not connect to https://conda.binstar.org/astrofrog/osx-64/
Could not connect to https://conda.binstar.org/astropy/osx-64/
                             0.3.0                np18py33_0  defaults        
                             0.3.0                np18py27_0  defaults        
                             0.3.0                np18py26_0  defaults        
                             0.3.1                np18py33_0  defaults        
                             0.3.1                np18py27_0  defaults        
                             0.3.1                np18py26_0  defaults        
                             0.3.2                np18py34_0  defaults        
                             0.3.2                np18py33_0  defaults        
                             0.3.2                np18py27_0  defaults        
                             0.3.2                np18py26_0  defaults        
                             0.4rc1               np18py34_0  defaults        
                             0.4rc1               np18py33_0  defaults        
                             0.4rc1               np18py27_0  defaults        
                             0.4rc1               np18py26_0  defaults        
                             0.4                  np18py34_0  defaults        
                             0.4                  np18py33_0  defaults        
                             0.4                  np18py27_0  defaults        
                             0.4                  np18py26_0  defaults        
                             0.4.1                np18py34_0  defaults        
                             0.4.1                np18py33_0  defaults        
                             0.4.1                np18py27_0  defaults        
                             0.4.1                np18py26_0  defaults   

@astrofrog
Copy link
Member

Ok - I think we should add back astropy-ci-helpers for now and we might be back to normal? Then we can try and phase it out more gradually?

@bsipocz
Copy link
Member Author

bsipocz commented Jun 15, 2016

Yes, that's a sensible workaround.

@astrofrog
Copy link
Member

By the way, I wonder if as ci-helpers gets adopted by more projects, we need either a twitter account or a simple status page so that if people are running into issues, they can see if we are working on it?

@bsipocz
Copy link
Member Author

bsipocz commented Jun 15, 2016

Maybe. Though I would go to the issue tracker first when trying to figure out such info rather than to twitter.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants