GitLab

Internal Change

PiperOrigin-RevId: 253658026

Project import generated by Copybara.

PiperOrigin-RevId: 253600369

Internal Change

PiperOrigin-RevId: 253581166

Internal Change

PiperOrigin-RevId: 233614147

Internal change

PiperOrigin-RevId: 232362580

This will help ensure that test coverage isn't missed when changes that
can impact OSX with clang are submitted. Although not perfect, testing
changes on OSX with clang is an ok proxy [for now] for testing changes on
FreeBSD with clang (testing on FreeBSD is non-trivial, as Travis CI doesn't
support operating systems other than Linux and OSX).

In order to support this, install the packages via homebrew using a
`addons::homebrew::packages` block (similar to `addons::apt::packages`
for Ubuntu), as documented in the Travis CI docs
( https://docs.travis-ci.com/user/installing-dependencies/

 ). While
here, try pushing apt* calls into the Travis config for Ubuntu, instead
of delaying the equivalent calls in the `ci/*.sh` scripts. Keep the
`ci/*.sh` scripts for ease of testing locally (and extend the OSX one to
install gcc 4.9 and llvm 3.9, like the travis config does).

In order to accomodate this change (and because the homebrew package for
llvm@3.9 doesn't automatically add clang*-3.9 to `$PATH`), `$PATH` needs
to be adjusted to find the llvm@3.9 toolchain.
Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>

This is inspired by work in http://go/gh/google/googletest/pull/2063 but in a separate commit

Removed global chmod +x for Travis scripts in favor of just applying it to PlatformIO builds.

Revert attempted template depth fix , a real fix is coming

Testing increasing -ftemplate-depth to fix clang 3.9

Add clang format check to one of the builds to provide indication that formatting is incorrect

Remove pre C++11

Bring travil yml back to the master branch state

Possibly related to travis env

There was an error that slipped through and only showed up on PR merge (https://travis-ci.org/google/googletest/jobs/364304396/config ) , we dont want that again

Had an instance where the breakage was not detected until the actual merge. Need to be better than that

Trying to get around mongoDB expired keys, etc