search for: gtest

...full log, I'll provide it. Here is a reduced log from the end: https://drive.google.com/file/d/1R5bLcCvgmgojkbDo6lB3jYBTBxweJP3v/view?usp=sharing What could be the problem? Thanks! :) SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/blitz/projects/llvm/utils/unittest/googletest/src/gtest.cc:474:31 in testing::internal::UnitTestOptions::PatternMatchesString(char const*, char const*) ==15959==WARNING: MemorySanitizer: use-of-uninitialized-value #0 0x739054 in testing::internal::UnitTestOptions::PatternMatchesString(char const*, char const*) /home/blitz/projects/llvm/utils/unittes...

...ed the command: cmake -G "Unix Makefiles" ../llvm -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX:PATH=/opt/llvm/current && gmake (I am aware of FreeBSD llvm/clang ports, but the source build should always succeed as well.) Yuri ---errors--- Scanning dependencies of target gtest [ 91%] Building CXX object utils/unittest/CMakeFiles/gtest.dir/googletest/src/gtest-all.cc.o In file included from /xpool/llvm/latest/llvm/utils/unittest/googletest/src/gtest-all.cc:42: In file included from /xpool/llvm/latest/llvm/utils/unittest/googletest/src/gtest.cc:132: /xpool/llvm/latest/l...

Please don't be alarmed by the failed compiles on llvm-ppc-darwin. They are likely not your fault. I'm trying to get a PPC build bot setup (arxan_bellini), and so far it's dying here: Linking CXX shared library ../../lib/libgtest.dylib Undefined symbols: "vtable for llvm::raw_ostream", referenced from: __ZTVN4llvm11raw_ostreamE$non_lazy_ptr in gtest.cc.o __ZTVN4llvm11raw_ostreamE$non_lazy_ptr in gtest-death-test.cc.o __ZTVN4llvm11raw_ostreamE$non_lazy_ptr in gtest-port.cc.o __ZTVN4llvm11r...

...lt;optimized out> #1 0x00007f4e2e32d0f7 in vaCreateContext () from /lib64/libva.so.2 No symbol table info available. #2 0x000055b48d29a419 in VAAPI::VAAPIFixture::doCreateContext (this=<optimized out>, resolution=..., expectation=@0x7ffea3f6e468: 4) at test_va_api_fixture.cpp:436 gtest_ar = {success_ = 32, message_ = {ptr_ = 0xebe6e1ca084a2300}} #3 0x000055b48d29ed34 in VAAPI::VAAPICreateContextToFail_CreateContextWithNoConfig_Test::TestBody (this=0x55b48e39c430) at test_utils.h:36 No locals. #4 0x000055b48d296e23 in testing::Test::Run (this=0x55b48e39c430) at ../test/gtest/src...

On Dec 27, 2008, at 7:41 PM, Misha Brukman wrote: > 2008/12/27 Mark Kromis <greybird at mac.com> > Just a curiosity question, why push for gtest vs Boost Test or a > different test suite? > I normally use Boost, and their test suite, so I'm more familiar > with that. So I was wondering is one better then the other, or is it > just that someone makes a patch for it? > > I looked more into Boost.Test to see what...

2008/12/27 Mark Kromis <greybird at mac.com> > Just a curiosity question, why push for gtest vs Boost Test or > a different test suite? > I normally use Boost, and their test suite, so I'm more familiar with that. > So I was wondering is one better then the other, or is it just that someone > makes a patch for it? > I looked more into Boost.Test to see what's in it....

2008/12/27 Mark Kromis <greybird at mac.com> > So are you planning on maintaining whatever test system, or just have them > as a pre-requisite. For example are you going to have the gtest > incorporated, or have them install it separately first? I was under the > impression that the user would have to install gtest first. > The current plan is to check in the unittest library into LLVM and build it as part of the test process, so the user doesn't have to do anything se...

Mark Kromis wrote: > On Dec 27, 2008, at 7:41 PM, Misha Brukman wrote: >> 2008/12/27 Mark Kromis <greybird at mac.com> >> Just a curiosity question, why push for gtest vs Boost Test or a >> different test suite? >> I normally use Boost, and their test suite, so I'm more familiar with >> that. So I was wondering is one better then the other, or is it just >> that someone makes a patch for it? I did a very minimal amount of research i...

Is no one else seeing this? (I've been seeing it for a few days) In file included from /usr/local/google/home/blaikie/dev/llvm/src/utils/unittest/googletest/gtest-all.cc:39: In file included from /usr/local/google/home/blaikie/dev/llvm/src/utils/unittest/googletest/include/gtest/gtest.h:57: In file included from /usr/local/google/home/blaikie/dev/llvm/src/utils/unittest/googletest/include/gtest/internal/gtest-internal.h:40: In file included from /usr/local/g...

...pretty much have to drink the "Boost > Kool-Aid" in order to use it. I agree, boost.test seems like a non-starter from many reasons. >> So are you planning on maintaining whatever test system, or just have >> them as a pre-requisite. For example are you going to have the gtest >> incorporated, or have them install it separately first? I was under >> the impression that the user would have to install gtest first. > So the plan is to take a snapshot of gtest and check it in to the LLVM > tree, rather than have it installed separately. Yes, we'd want...

...ing 'check-msan'. On Sun, May 12, 2013 at 9:10 PM, David Blaikie <dblaikie at gmail.com> wrote: > Is no one else seeing this? (I've been seeing it for a few days) > > In file included from > > /usr/local/google/home/blaikie/dev/llvm/src/utils/unittest/googletest/gtest-all.cc:39: > In file included from > > /usr/local/google/home/blaikie/dev/llvm/src/utils/unittest/googletest/include/gtest/gtest.h:57: > In file included from > > /usr/local/google/home/blaikie/dev/llvm/src/utils/unittest/googletest/include/gtest/internal/gtest-internal.h:40: >...

...the new fix for avoiding the Support library dependency set from the 'required_libraries = Support' in llvm/utils/unittest/LLVMBuild.txt is not read it for LLVM_LINK_LLVM_DYLIB. The new patch modifies llvm_add_library() in cmake/modules/AddLLVM.cmake to manually set the LLVMBUILD_LIB_DEPS_gtest property to LLVM when LLVM_LINK_LLVM_DYLIB is set and the library name is gtest rather than read from the tools/llvm-config/LibraryDependencies.inc generated by llvm-build. Jack ps As soon as this patch lands, I'll look at trying to rework the unittests handling of the LLVM...

...he "Boost > > Kool-Aid" in order to use it. > > I agree, boost.test seems like a non-starter from many reasons. > > >> So are you planning on maintaining whatever test system, or just have > >> them as a pre-requisite. For example are you going to have the gtest > >> incorporated, or have them install it separately first? I was under > >> the impression that the user would have to install gtest first. > > So the plan is to take a snapshot of gtest and check it in to the LLVM > > tree, rather than have it installed separately....

...uot;) + set(link_components "") + else() + list(REMOVE_ITEM link_components ${LLVM_DYLIB_COMPONENTS}) + endif() + endif() target_link_libraries(${executable} LLVM) endif() However the avoiding the accidental linkage of libLLVMSupport with libLLVM and libgtest for the unittests was really tricky as two different mechanisms to pass LLVMSupport are in play. The underlying problem was that the python based llvm-build tool was forcing a dependency on LLVMSupport for libgtest according to the required_libraries entry for the gtest library in utils/unittest/L...

Hi folks, I'm using gcc 4.8.1 and I'm getting these warnings on every googletest file: src/llvm/utils/unittest/googletest/include/gtest/gtest-typed-test.h:239:47: warning: anonymous variadic macros were introduced in C99 [-Wvariadic-macros] # define REGISTER_TYPED_TEST_CASE_P(CaseName, ...) \ ^ It seems a gtest infrastructure file, so maybe we should just ignore that warning on the un...

$(llvm-config --libs | tr " " "\n" | grep gtest) returns: -lgtest_main -lgtest instead of non-valid: -lLLVMgtest_main -lLLVMgtest It also fixes: $(ld): cannot find -lLLVMgtest $(ld): cannot find -lLLVMgtest_main --- unittests/Makefile.unittest | 2 +- utils/llvm-build/llvmbuild/componentinfo.py | 4 ++-- utils/llvm-build...

On Sat, Dec 27, 2008 at 6:56 PM, Mark Kromis <greybird at mac.com> wrote: > > On Dec 27, 2008, at 7:41 PM, Misha Brukman wrote: > > 2008/12/27 Mark Kromis <greybird at mac.com> > >> Just a curiosity question, why push for gtest vs Boost Test or >> a different test suite? >> I normally use Boost, and their test suite, so I'm more familiar with >> that. So I was wondering is one better then the other, or is it just that >> someone makes a patch for it? >> > > I looked more into Boost....

Hello, I am trying to configure a volume using DHT, however after I mount it, the mount point looks rather strange and when I try to do 'ls' on it I get: ls: /mnt/gtest: Stale NFS file handle I can create files and dirs in the mount point, I can list them but I cant list the mount point itself. Example: the folume is mounted on /mnt/gtest [root at storage2]# ls -l /mnt/ ?--------- ? ? ? ? ? gtest If I try to list the mountpoint: [root a...

...0x000000000046c749 in InputGraphTest_Observer_Test::TestBody (this=0xa1e6b0) at /home/rengolin/devel/llvm/src/llvm/tools/lld/unittests/DriverTests/InputGraphTest.cpp:201 #8 0x0000000000479bda in testing::Test::Run (this=0xa1e6b0) at /home/rengolin/devel/llvm/src/llvm/utils/unittest/googletest/src/gtest.cc:2162 #9 0x000000000047abd0 in testing::TestInfo::Run (this=0xa1d6f0) at /home/rengolin/devel/llvm/src/llvm/utils/unittest/googletest/src/gtest.cc:2309 #10 0x000000000047adc5 in testing::TestCase::Run (this=0xa1cfe0) at /home/rengolin/devel/llvm/src/llvm/utils/unittest/googletest/src/gtest.cc:24...

On Sun, Oct 12, 2008 at 11:13 AM, Keir Mierle <mierle at gmail.com> wrote: > Justs to chime in: I'm one of the gtest devs. I'd like to add that gtest is > very portable, more so than llvm; it even works on WinCE and blackberry. If > there are specific features needed by LLVM, depending on what it is I may be > able to get it into gtest. I noticed that gtest uses fork to test some code points (which...