similar to: [LLVMdev] Whats GoogleTest ?

> What is googletest ? Framework for units tests in llvm. http://code.google.com/p/googletest/ > Its aufully messy warnings wise on Cygwin. If you have gcc 3.X you are going to get a bunch of warnings. What gcc are you using? -Tanya

Hi Kees, You added some support for Minix to LLVM's copy of googletest: http://llvm.org/viewvc/llvm-project?view=rev&revision=100895 Is it still being used? If so, would you mind pushing these patches upstream to the googletest project: http://code.google.com/p/googletest/ Otherwise we may drop them, because it makes it harder to import new releases of googletest into the LLVM

+Chandler who might have some thoughts on this. Could you provide an example here of the motivation for the feature you're missing? Might help motivate the discussion (and/or we'll end up nitpicking how it could be done differently without that feature... - which is sort of where I'm going with this. Combinatorial test case expansion does seem a bit suspicious to me - I'd hope we

Hi all, I'm currently writing some unit tests for some debug line error handling code I'm working on (see e.g. https://reviews.llvm.org/D44382), and I just ran into an annoying disabled feature in gtest, specifically the "Combine" feature for use in combinatorially generating parameterised tests. A FIXME comment in ProfileData\CoverageMappingTest.cpp suggests that I'm not

On Thu, Mar 15, 2018 at 9:09 PM, David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> wrote: > +Chandler who might have some thoughts on this. > > Could you provide an example here of the motivation for the feature you're > missing? Might help motivate the discussion (and/or we'll end up nitpicking > how it could be done differently without that feature... - which

Thanks. The motivating example can be seen in this review: https://reviews.llvm.org/D44382. In that review, I am unit testing .debug_line parsing, specifically, the behaviour when the parser is fed a malformed section. Most of the code under test goes through some slight variations in the code path, depending on a) the DWARF version (interesting cases are 3, 4 and 5), and b) whether the DWARF is

On Thu, Mar 15, 2018 at 11:10 AM David Blaikie via llvm-dev < llvm-dev at lists.llvm.org> wrote: > +Chandler who might have some thoughts on this. > FWIW, I have no concerns about updating to a modern googletest. More modern the better IMO if someone is willing to do the work to make sure it works on all our platforms, etc. However: > Could you provide an example here of the

On 19 March 2018 at 19:56, Chandler Carruth <chandlerc at gmail.com> wrote: > On Thu, Mar 15, 2018 at 11:10 AM David Blaikie via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> +Chandler who might have some thoughts on this. >> > > FWIW, I have no concerns about updating to a modern googletest. More > modern the better IMO if someone is willing to do

Hi Jay, >> yes, they are annoying aren't they. They all come from google's unittest >> library. I think it is best to fix them upstream at google. > > We're using googletest 1.5.0. These warnings seem to be fixed in > 1.6.0, so here's a patch to upgrade us. Disclaimer: I've only tested > this by doing "make check-all" on Linux/x86_64. >

On 24 July 2011 10:59, Duncan Sands <baldrick at free.fr> wrote: > Hi Edward, > >> Building of llvm with gcc-4.5.2-1 gives these warnings: >> >> 1) Building FileManagerTest >> >> "llvm[4]: Compiling FileManagerTest.cpp for Debug+Asserts build >> C:/Programming/VersionControl/llvm/tools/clang/unittests/Basic/FileManagerTest.cpp: >> In

LLVMers, The 2.5 pre-release2 is finally available for testing: http://llvm.org/prereleases/2.5/ If you have time, I'd appreciate anyone who can help test the release. Please do the following: 1) Download/compile llvm source, and either compile llvm-gcc source or use llvm-gcc binary (please compile llvm-gcc with fortran if you can). 2) Run make check, send me the testrun.log 3) Run

On May 19, 2008, at 9:13 PM, Razvan Aciu wrote: > I tested this pre-release on MSVC and I noted that none of the > submitted > patches (mine or others) were applied. > So the llvm 2.3 will not compile out of the box in MSVC? > Please provide me with a link to the patch(s) that need to be applied (llvm-commits archive email). I only apply patches that have been sent to me and

Google Test requires these CPP FLAGS "-Wno-missing-field-initializers - Wno-variadic-macros" in order to not output warnings. However, these flags are only available with gcc 4.X. We don't want to prevent users from being able to build with gcc 3.X which is the current situation (http://llvm.org/PR3487 ). I've disabled building Google Test in the 2.5 branch. Hopefully

Just a reminder, please complete your testing by May 21st! Thanks, Tanya ---------- Forwarded message ---------- Date: Tue, 13 May 2008 00:25:41 -0700 From: Tanya Lattner <tonic at nondot.org> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Subject: 2.3 Pre-release available for testing LLVMers, The 2.3 pre-release is available for testing:

Thank you! It seems like new changes in .rst files are picked up quickly now. -- Alex On Thu, Feb 14, 2019 at 7:33 PM Tanya Lattner <tonic at nondot.org> wrote: > This should all be fixed now. > > Thanks, > Tanya > > > On Feb 14, 2019, at 9:50 AM, Tanya Lattner <tonic at nondot.org> wrote: > > Yes, I am working on it. The sub-projects are still having

I'm seeing some test failures for unit tests for msan (check-msan) happening in googletest, which I find weird. I'm on Arch Linux, with r342711. Below is one type of error that I see. The full log is 416MB (!) big. My guess is that those errors are related, but if anyone needs the full log, I'll provide it. Here is a reduced log from the end:

Yes, I am working on it. The sub-projects are still having issues but the other documentation has been fixed. -Tanya > On Feb 14, 2019, at 3:53 AM, Alexander Kornienko <alexfh at google.com> wrote: > > Tanya, friendly ping. > > On Mon, Feb 11, 2019 at 3:21 PM Alexander Kornienko <alexfh at google.com <mailto:alexfh at google.com>> wrote: > Hi Tanya, >

Hello all, we are trying to convert some of the lldb tests to lit (for these specific tests we are using the googletest format). One of our requirements is that we are able to run these tests remotely, so that we are able to verify that we can debug e.g. android arm binaries even though our development environment runs x86 linux). As far as I am aware, right now there is no support for that in

This is my patch for MSVC 2008 and it was applied by Chris: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20080512/062390.html I tested it and it is ok for the 2.3 release. Razvan ----- Original Message ----- From: "Tanya Lattner" <tonic at nondot.org> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Tuesday, May 20, 2008 7:40 AM

Hello Jay, At the time I submitted those patches I also submitted them to googletest. As far as I know they got accepted, although I didn't verify that. I am no longer working on the Minix project, but since the Minix project is most definitely using llvm, I am cc:-ing this to the Minix developers mailing list. Perhaps they want to respond to this. -- Kees On 27 Jul 2011, at 11:43, Jay