-
-
Notifications
You must be signed in to change notification settings - Fork 718
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
Comments
Seems to be pretty consistently on python 3.8 during the |
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. |
+1, as the Travis tests have been consistently failing, I've primarily been relying on our Windows tests |
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. |
I never experienced a segfault on github actions (Linux/Windows/MacOS) over ~500 jobs. |
That's reassuring thanks @crusaderky. Will close. |
There appears to be a segfault on CI. Haven't debugged further.
See for example https://travis-ci.org/github/dask/distributed/jobs/750955092
The text was updated successfully, but these errors were encountered: