Sanitizer builds are broken (regressed on travis)

[springmeyer]

travis-ci/travis-ci#8840 notes what we are seeing as of today for node-cpp-skel and all repos based on it: the sanitizer job is crashing due to a regression in travis.

LeakSanitizer has encountered a fatal error

/cc @mapbox/core-tech

[mapsam]

This was fixed! https://travis-ci.org/mapbox/node-cpp-skel/jobs/308170250 is now 🍏 again.

[mapsam]

Unfortunately, this is popping up again 😢 https://travis-ci.org/mapbox/vtquery/jobs/312013091

[springmeyer]

@mapsam - that looks slightly different to me. I also see that the LSAN debugging flag is on still in that build. Can you turn it off, try another build, and then post what you are seeing?

[springmeyer]

Closing, looks like @mapsam resolved the vtquery specific issue by removing LSAN_OPTIONS in mapbox/vtquery@18b682b#diff-354f30a63fb0907d4ad57269548329e3

[springmeyer]

Re-opening. This is now happening again per travis-ci/travis-ci#8836 (comment). Going to keep this open as a way of tracking this for @mapbox/core-tech (since all node-cpp-skel and hpp-skel based repos that leverage the sanitizers will have that job failing).

For now I propose:

• letting the job fail, ignore for now
• we'll wait a week or so for travis to try to fix and close Regression: Chrome fails to start due to incorrect default chrome-sandbox permissions travis-ci/travis-ci#8836 (comment)
• if the problem persists then we'll look at applying a workaround (like sudo: true, but ideally we'll not need to do anything)

Also: moving to circleci is another option, but let's not do this for this reason. Rather let's build up knowledge of circleci 2.0 and its merits and not worry about a mass migration yet.