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

Segmentation fault on travis #4387

Closed
fjetter opened this issue Dec 22, 2020 · 6 comments · Fixed by #4504
Closed

Segmentation fault on travis #4387

fjetter opened this issue Dec 22, 2020 · 6 comments · Fixed by #4504

Comments

@fjetter
Copy link
Member

fjetter commented Dec 22, 2020

There appears to be a segfault on CI. Haven't debugged further.

See for example https://travis-ci.org/github/dask/distributed/jobs/750955092

@fjetter
Copy link
Member Author

fjetter commented Jan 11, 2021

Seems to be pretty consistently on python 3.8 during the test_worker.py tests

@jacobtomlinson
Copy link
Member

Yeah I've also noticed this.

I've been trying to push forwards with #4218. I'd hate to waste effort tracking down a Travis specific issue and then move CI.

@jrbourbeau
Copy link
Member

I'd hate to waste effort tracking down a Travis specific issue and then move CI

+1, as the Travis tests have been consistently failing, I've primarily been relying on our Windows tests

@jakirkham
Copy link
Member

Agree with others that time is likely better spent migrating to GitHub Actions than debugging Travis CI. If we still see this issue on GitHub Actions, then it would be worth debugging further.

@crusaderky
Copy link
Collaborator

I never experienced a segfault on github actions (Linux/Windows/MacOS) over ~500 jobs.

@jacobtomlinson
Copy link
Member

That's reassuring thanks @crusaderky. Will close.

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

Successfully merging a pull request may close this issue.

5 participants