[llvm-dev] Bot failure re: [llvm] d4d80a2 - Bump googletest to 1.10.0

[David Blaikie via llvm-dev]

Hopefully 7f5d8e655965c0347c2a05f65e63dec4490a9fa0 should address that.

On Sun, May 16, 2021 at 7:38 AM Hubert Tong via llvm-commits <
llvm-commits at lists.llvm.org> wrote:

> @benny.kra at gmail.com <benny.kra at googlemail.com>,
>
> The good news is that the other failures I saw on our internal build
> environments were resolved by forcing a clean build.
>
> I can confirm that the following failure was still reproducible from a
> clean build though. Is there an ETA on a fix?
>
> -- HT
>
> On Sat, May 15, 2021 at 1:49 PM Hubert Tong <
> hubert.reinterpretcast at gmail.com> wrote:
>
>> This failure is still occurring:
>> https://lab.llvm.org/buildbot/#/builders/36/builds/8361/steps/12/logs/stdio
>>
>> /home/buildbots/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/install/stage1/bin/clang++
>>  -DGTEST_HAS_RTTI=0 -D_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS
>> -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Iunittests/IR
>> -I/home/buildbots/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/unittests/IR
>> -Iinclude
>> -I/home/buildbots/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/include
>> -I/home/buildbots/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/utils/unittest/googletest/include
>> -I/home/buildbots/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/utils/unittest/googlemock/include
>> -fPIC -fvisibility-inlines-hidden -Werror -Werror=date-time
>> -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter
>> -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic
>> -Wno-long-long -Wc++98-compat-extra-semi -Wimplicit-fallthrough
>> -Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor
>> -Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion
>> -Wmisleading-indentation -fdiagnostics-color -ffunction-sections
>> -fdata-sections -O3 -DNDEBUG    -Wno-variadic-macros
>> -Wno-gnu-zero-variadic-macro-arguments -fno-exceptions -fno-rtti -UNDEBUG
>> -Wno-suggest-override -std=c++14 -MD -MT
>> unittests/IR/CMakeFiles/IRTests.dir/PassBuilderCallbacksTest.cpp.o -MF
>> unittests/IR/CMakeFiles/IRTests.dir/PassBuilderCallbacksTest.cpp.o.d -o
>> unittests/IR/CMakeFiles/IRTests.dir/PassBuilderCallbacksTest.cpp.o -c
>> /home/buildbots/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/unittests/IR/PassBuilderCallbacksTest.cpp
>> In file included from
>> /home/buildbots/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/unittests/IR/PassBuilderCallbacksTest.cpp:9:
>> In file included from
>> /home/buildbots/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/include/llvm/Testing/Support/Error.h:16:
>> In file included from
>> /home/buildbots/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/utils/unittest/googlemock/include/gmock/gmock.h:61:
>> In file included from
>> /home/buildbots/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/utils/unittest/googlemock/include/gmock/gmock-function-mocker.h:39:
>> In file included from
>> /home/buildbots/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/utils/unittest/googlemock/include/gmock/gmock-generated-function-mockers.h:49:
>> /home/buildbots/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/utils/unittest/googlemock/include/gmock/gmock-spec-builders.h:1301:3:
>> error: definition of implicit copy constructor for
>> 'MockSpec<llvm::PreservedAnalyses (llvm::Loop &,
>> llvm::AnalysisManager<llvm::Loop, llvm::LoopStandardAnalysisResults &> &,
>> llvm::LoopStandardAnalysisResults &, llvm::LPMUpdater &)>' is deprecated
>> because it has a user-declared copy assignment operator
>> [-Werror,-Wdeprecated-copy]
>>   GTEST_DISALLOW_ASSIGN_(MockSpec);
>>   ^
>>
>> I will note there are other failures we are observing in configurations
>> (using vanilla monorepo source) that we have running downstream that may be
>> related to the same change. I am not sure how much progress a "fix forward"
>> strategy is going to make over a weekend.
>>
>> -- HT
>>
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210516/f140cecb/attachment.html>