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

Effectively cache astrometry, et al, on travis #711

Closed
jamessynge opened this issue Oct 22, 2018 · 6 comments
Closed

Effectively cache astrometry, et al, on travis #711

jamessynge opened this issue Oct 22, 2018 · 6 comments
Assignees
Labels
good first issue stale? Potentially stale issue that can be closed. Testing
Milestone

Comments

@jamessynge
Copy link
Contributor

jamessynge commented Oct 22, 2018

Builds currently fail if they can't download the astrometry index files. I believe we are making some use of the Travis caching feature, but not enough to prevent this problem.

@wtgee
Copy link
Member

wtgee commented Oct 22, 2018

I have a branch where I started some work on this. I'll see if it's worth pushing.

@jamessynge
Copy link
Contributor Author

Assigning it to you in hopes that your branch has something worthwhile in it. Several recent builds have failed due these problems.

@jamessynge
Copy link
Contributor Author

Alternately, point me to your branch.

@jamessynge
Copy link
Contributor Author

I've made lots of progress on understanding how to set this up (#712), but now am stymied by astrometry.net being offline again. It seems like we should cache critical dependencies in GCS.

FWIW, it appears that I spoiled the cache for #712 with one bad command which then meant that the next build of that PR didn't have a cache to pull from, so needed to read from astrometry.net. I'm going to try to get that PR thing submitted today so that future builds will hopefully be better able to use the travis provided caching facility.

@wtgee
Copy link
Member

wtgee commented Mar 29, 2019

@jamessynge did we ever get anywhere with this?

If anything I am thinking that as we move more toward a docker-based approach it won't be an issue. I know we are also storing a few things in our own storage bucket, which it doesn't appear we are using but which we could.

@wtgee wtgee added this to the V1.0 milestone Feb 17, 2020
@wtgee wtgee added stale? Potentially stale issue that can be closed. Testing good first issue labels Feb 17, 2020
@wtgee
Copy link
Member

wtgee commented Jun 1, 2020

Made stale by #951. Please re-open a new issue if needed. Thanks!

@wtgee wtgee closed this as completed Jun 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue stale? Potentially stale issue that can be closed. Testing
Projects
None yet
Development

No branches or pull requests

2 participants