Ember Try scenario failing on Travis with a Segmentation fault

Hi! I’m investigating a Travis failure in one of my Ember Try scenarios and am looking for any guidance. I have no idea if this has anything to do with Ember Try but figured I’d start here.

Here’s the failure. If you look back at the full build you’ll see the same failure for all Versioned tests.

When I tried one of them locally by running

ember try:one ember-lts-2.18

it passed with no problem.

My next guess was the Segmentation fault had something to do with Travis’ cache. I thought maybe it was due to all the PRs Dependabot was opening. I went back to Travis, deleted all caches, and re-ran master. No change, the fault still happened.

I then thought it might have been due to a code change on my end, so I went back to the last-passing build and re-ran it. I saw the same failures on the Versioned tests.

---

Any idea for what could be going on? Is there possibly a memory leak that I’m not seeing locally but that is causing Travis to blow up?

Any help much appreciated!

[kategengler]

Wow! So many levels…

(I am continually amazed anything ever works)

[rwjblue]

Going to close for now, happy to reopen if folks think this is still an issue.