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

Travis failing on segfault at print_versions #2683

Closed
max-sixty opened this issue Jan 15, 2019 · 4 comments
Closed

Travis failing on segfault at print_versions #2683

max-sixty opened this issue Jan 15, 2019 · 4 comments

Comments

@max-sixty
Copy link
Collaborator

master is breaking on both the docs and python3.6 print_versions: https://travis-ci.org/pydata/xarray/jobs/479834129

/home/travis/.travis/job_stages: line 104:  3514 Segmentation fault      (core dumped) python xarray/util/print_versions.py
The command "python xarray/util/print_versions.py" failed and exited with 139 during .

Has anyone seen this before? I can't replicate locally, but I likely don't have the same dependencies

@max-sixty max-sixty changed the title Travis failing on OOM at print_versions Travis failing on segfault at print_versions Jan 16, 2019
@jhamman
Copy link
Member

jhamman commented Jan 17, 2019

This is unfortunate and indeed tricky to diagnose. My guess is there is a spurious bad build somewhere in anaconda land causing this error. Let's wait a day or so to see if things resolve on their own, if now, there are other options for figuring out the offending library.

@benbovy
Copy link
Member

benbovy commented Jan 17, 2019

rasterio might be guilty here. I could replicate the segmentation fault on a linux VM. It worked after uninstalling it. I see on https://conda-forge.org/status/ that rasterio has not been rebuild yet with the new compilers. Since the compiler migration has been completed earlier this week, this might be related.

@benbovy
Copy link
Member

benbovy commented Jan 17, 2019

xref: conda-forge/rasterio-feedstock#98

@max-sixty
Copy link
Collaborator Author

Does nyone have an idea whether this will be resolved in a couple of days? Otherwise I can try and put a temporary fix in (there's one described in that issue, but I don't have experience with conda so can't assess whether it's likely to be successful)

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

No branches or pull requests

3 participants