Segmentation fault on travis #4387

Activity

1. fjetter commented on Jan 11, 2021

   

   fjetter

   on Jan 11, 2021

   MemberAuthor

   More actions

   Seems to be pretty consistently on python 3.8 during the test_worker.py tests
2. jacobtomlinson commented on Jan 11, 2021

   

   jacobtomlinson

   on Jan 11, 2021

   Member

   More actions

   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.

   👍React with 👍1Reacted by jakirkham
3. jrbourbeau commented on Jan 11, 2021

   

   jrbourbeau

   on Jan 11, 2021

   Member

   More actions

   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

   👍React with 👍1Reacted by jakirkham
4. jakirkham commented on Jan 11, 2021

   

   jakirkham

   on Jan 11, 2021

   Member

   More actions

   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.

   👍React with 👍3Reacted by James Bourbeau, Florian Jetter and Jacob Tomlinson
5. crusaderky commented on Feb 24, 2021

   

   crusaderky

   on Feb 24, 2021

   Collaborator

   More actions

   I never experienced a segfault on github actions (Linux/Windows/MacOS) over ~500 jobs.
6. jacobtomlinson commented on Feb 24, 2021

   

   jacobtomlinson

   on Feb 24, 2021

   Member

   More actions

   That's reassuring thanks @crusaderky. Will close.

   👍React with 👍1Reacted by jakirkham
7. jacobtomlinson

   closed this as completedon Feb 24, 2021