Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
TST: Tests failures in coordinates caused by IndexError in IERS with numpy-dev
See original GitHub issueA blame on the LOC pointed to #9226 though the PR itself was green. 🤷♀️
@mhvk , any idea?
Example log: https://travis-ci.org/astropy/astropy/jobs/585668145
UPDATE
Looks like numpy-dev job did pass in https://travis-ci.org/astropy/astropy/builds/585637569 (“about 2 hours ago” at the time of writing this with numpy 1.18.0.dev0+07a7eb5) but failed in https://travis-ci.org/astropy/astropy/jobs/585641053 (also “about 2 hours ago” with 1.18.0.dev0+07a7eb5). The PR merged seems unrelated to IERS nor coordinates. And no changes were merged into numpy-dev since 8 hours ago. Then, more tests failed on our end in the next run (https://travis-ci.org/astropy/astropy/jobs/585668145). Did IERS data server change something?
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ah, that means it might have been the same problem: for me, it seems the
finals2000Afile was downloaded only partially and it was quite hard to remove it and retry. Maybe something similar happened for travis. In any case, that would seem part of #9182 - so, for once no need to raise a new issue!Fortunately, I had started on something else… But while testing that, I found a similar issues, which resulted from the IERS-A table not downloading completely. I think we do need to circumvent that by having a cached version or so…