[llvm-dev] [cfe-dev] Rotten Green Tests project (original) (raw)

via llvm-dev llvm-dev at lists.llvm.org
Mon Mar 1 07:25:32 PST 2021

Thanks for the feedback, David!

Initial gut reaction would be this is perhaps a big enough patch/divergence from upstream gtest that it should go into upstream gtest first

I was not aware that googletest itself was open source, as opposed to something Google-internal that you guys had permission to put into LLVM. Although it makes sense for it to be open source on its own.

As I mentioned in the writeup, it would be great to get feedback from people who actually understood googletest, try it on other platforms I don't have available (e.g., Mac) and ideally help solve a couple of the problems I have run into.

In the meantime, obviously I can keep patching up our unittests where RGT has found something.

& maybe sync'ing up with a more recent gtest into LLVM? Though I realize that's a bit of a big undertaking (either/both of those steps).

A quick skim through the LLVM git log suggests that we've done some things to connect with LLVM-ish ways of doing things, e.g., using raw_ostream instead of std::ostream. Other things, such as new targets/environment (I saw mention of MinGW) probably also should have been done upstream. Perhaps it is not obvious to non-Googlers that there is an upstream project (did I mention I was not aware?).

The last upgrade was to 1.8.0 in Jan 2017 by Chandler. I see upstream has tagged 1.8.1 and 1.10.0 since then (no 1.9.0). Chandler's log message does say "minimizing local changes" which sounds somewhat hopeful. There have been changes since then. Looking at a handful of diffs, I see some things guarded by a conditional with LLVM in the name, and more where the change was simply made with no effort to identify it as local. This suggests we (LLVM) have made some effort to make future merges not-horrible, but it would still be a chunk of work.

As a 10% project, I think I'd prefer to concentrate on fixing our own unittests first, but work on integrating with upstream googletest rather than pursue the RGT infrastructure as an LLVM mod, when I've gotten our test fixes sorted out.

How does this compare to other local patches to gtest we have?

No clue. I'd have to do a diff against the upstream project, and sort out which are due to LLVM's stripping-down procedure and which are actual features & fixes we've done. However, as a guess it's overall significantly bigger than anything else done locally.

I have tried to minimize RGT's intrusion into the base googletest code (well, LLVM's base googletest code). Most of it is in a new header and .cc file. After proper integration with the upstream project, that might not remain true, though.

Thanks, --paulr

More information about the llvm-dev mailing list