New issue
Advanced search Search tips

Issue 908676 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Nov 27
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

ToTAndroidOfficial failing during gclient runhooks update.py

Project Member Reported by chcunningham@chromium.org, Nov 27

Issue description

Started to fail here: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/ToTAndroidOfficial/751

Red ever since. 

Failing during make of static analysis libs

[1036/2346] Building CXX object lib/Analysis/CMakeFiles/LLVMAnalysis.dir/StackSafetyAnalysis.cpp.o
FAILED: lib/Analysis/CMakeFiles/LLVMAnalysis.dir/StackSafetyAnalysis.cpp.o 
/usr/bin/c++  -DGTEST_HAS_RTTI=0 -D_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Ilib/Analysis -I/b/s/w/ir/cache/builder/src/third_party/llvm/lib/Analysis -I/usr/include/libxml2 -Iinclude -I/b/s/w/ir/cache/builder/src/third_party/llvm/include -DLLVM_FORCE_HEAD_REVISION -fPIC -fvisibility-inlines-hidden -std=c++11 -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wno-maybe-uninitialized -Wdelete-non-virtual-dtor -Wno-comment -ffunction-sections -fdata-sections -O3    -UNDEBUG  -fno-exceptions -fno-rtti -MD -MT lib/Analysis/CMakeFiles/LLVMAnalysis.dir/StackSafetyAnalysis.cpp.o -MF lib/Analysis/CMakeFiles/LLVMAnalysis.dir/StackSafetyAnalysis.cpp.o.d -o lib/Analysis/CMakeFiles/LLVMAnalysis.dir/StackSafetyAnalysis.cpp.o -c /b/s/w/ir/cache/builder/src/third_party/llvm/lib/Analysis/StackSafetyAnalysis.cpp
In file included from /usr/include/c++/4.8/cassert:43:0,
                 from /b/s/w/ir/cache/builder/src/third_party/llvm/include/llvm/IR/IntrinsicInst.h:36,
                 from /b/s/w/ir/cache/builder/src/third_party/llvm/lib/Analysis/StackSafetyAnalysis.cpp:16:
/b/s/w/ir/cache/builder/src/third_party/llvm/lib/Analysis/StackSafetyAnalysis.cpp: In member function 'bool {anonymous}::StackSafetyDataFlowAnalysis::updateOneUse({anonymous}::UseInfo&, bool)':
/b/s/w/ir/cache/builder/src/third_party/llvm/lib/Analysis/StackSafetyAnalysis.cpp:465:16: error: 'struct {anonymous}::PassAsArgInfo' has no member named 'Range'
     assert(!CS.Range.isEmptySet() &&


Thakis@ can you help or redirect? 
 
Cc: vtsyrklevich@chromium.org
vtsyrklevich@ explained on IRC that this is typcial of ToT bots and should now be fixed. All thats left is to verify the future builds go green 

[17:58] <vtsyrkle1ich> chcunningham: That's an upstream LLVM failure because it's a ToT bot, it should resolve once upstream is fixed (which it should now be)
[17:59] <chcunningham> thanks. so the "tree" implied by "ToT" for these bots is upstream llvm?
[18:00] <chcunningham> (my first time seeing these bots)
[18:00] == mavhc [~mavhc@cpc77319-basf12-2-0-cust433.12-3.cable.virginm.net] has quit [Ping timeout: 250 seconds]
[18:01] <vtsyrkle1ich> yes, it's for tracking that tip-of-tree for the toolchain can still compile chromium (and that no optimization/etc. bugs have crept in that would now cause test failures)
[18:01] == vtsyrkle1ich has changed nick to vtsyrklevich
Owner: h...@chromium.org
Yes, all the ToT bots are LLVM ToT. They have a dedicated waterfall (https://ci.chromium.org/p/chromium/g/chromium.clang/console), and a dedicated sheriff rotation (this week, hans).

Regular sheriffs shouldn't look at them.
Status: Fixed (was: Untriaged)
The bot is green again: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/ToTAndroidOfficial/761

Sign in to add a comment