Paul T Robinson

@derekmauro According to https://cla.developers.google.com/clas, [email protected] is on the corporate CLA https://cla.developers.google.com/about/android-legacy-corporate I don't know why the workflow check is failing, that would seem to be a problem on your side?

Thanks Derek! Very happy to have the bureaucratic stuff over with. It was pretty clear from the googletest commit history that this is an internal thing that Google chooses to...

I've pushed an update to make the default for `--gtest_treat_rotten_as_pass` configurable, and default to `true` so existing test suites won't suddenly start failing. Filed #4254 regarding my failure to get...

`bazel build //:gtest --cxxopt=-std=c++14` (as suggested in the other issue) completes with no errors. Not clear how to build/run the googletest tests under bazel, though.

`bazel build //googletest/test:gtest_all_tests --cxxopt=-std=gnu++14` looks like it is compiling everything okay, but failing to link because it can't find my new APIs. They're all decorated with `GTEST_API_`. The top-level BUILD.bazel...

Found the build problem--bazel builds modules individually, but CMake uses gtest-all.cc, which allowed some sloppiness to creep in. That's fixed. Speculatively tried `bazel test //:gtest` which complained "No test targets...

Hi Derek, good news and bad news. The good news is, I got my new tests to build and run under Bazel. You might want to look at the BUILD.bazel...

See #4552 for a revised patch that works in Google's Bazel environment, but is less effective.

I'm retiring soon, if someone else wants to pick this up the PRs are still here.

My impression was that the labels auto-subscribed the members of the associated list, which is impractical for lists the size of llvm-commits. Maybe I'm wrong about how that works. Currently,...