Think this might be due to the following: # Clang is used by all builds so it is part of the 'common' library group even # though its LLVM libraries are installed to $PREFIX_UNINSTRUMENTED. if [ -n "$F_COMMON" -o -n "$F_LLVM" ]; then build_llvm normal fi
With Mike's patch e87fb79076d5ae2838cad6b63a78066a7853fb20, we try to fully remove a prefix before rebuilding it. So, in the case that we decide just to rebuild 'uninstrumented', we'll delete the LLVM installation, and then reinstall but forgot to rebuild/reinstall LLVM, since it builds as part of the 'common' group and not the 'uninstrumented' group. Mike, can you take a look at this? Or can we revert your patch for the time being until it's sorted out? Seems to be corrupting workspaces left and right (more than the problem it's meant to solve was) -Todd On Wed, Feb 1, 2017 at 10:10 PM, Todd Lipcon <[email protected]> wrote: > Just hit the same "could not find LLVM" cmake issues on several builds. I > went looking at the build history and found the sequence of builds that had > run in the same workspace > > *19:57:31 to 20:59:25* > http://104.196.14.100/job/kudu-gerrit/BUILD_TYPE=TSAN/6061/console > - building hash b24ab3e38da50327e0e2b35f88f9cfa318e1328f > - rebuild thirdparty "common" and "tsan" dependencies > I attached this build log gzipped in case it disappears. > > *20:59:28 to 21:06:04* > http://104.196.14.100/job/kudu-gerrit/BUILD_TYPE=RELEASE/6065/consoleFull > - building hash 0e0ccb58dec08ab709d6add3d964efbc0b9cb01b > - decided it needed to rebuild thirdparty, but I don't see any logs about > building LLVM > - eventually failed with the "cannot find LLVM" cmake issue > > > *21:06:16 to 21:06:26* > http://104.196.14.100/job/kudu-gerrit/6064/BUILD_TYPE=ASAN/console > [failed with the LLVM issue] > > *21:06:29 to 21:06:39* > http://104.196.14.100/job/kudu-gerrit/6064/BUILD_TYPE=LINT/console > [failed with the LLVM issue] > > *21:06:39 to 21:32:22* > http://104.196.14.100/job/kudu-gerrit/6064/BUILD_TYPE=TSAN/consoleFull > [failed because of a bunch of these: > 21:11:06 ldd: /home/jenkins-slave/workspace/kudu-2/thirdparty/installed/ > uninstrumented/bin/llvm-symbolizer: No such file or directory > 21:11:06 failed to run ldd on /home/jenkins-slave/ > workspace/kudu-2/thirdparty/installed/uninstrumented/bin/llvm-symbolizer > > so I'm thinking whatever we are looking for of interest might be in the > build logs of that first build. I couldn't find any builds retained for > earlier builds in the same workspace. > > Can someone who has been working on this thirdparty build stuff the last > couple days take a look? The failing precommits are pretty painful. > > -- > Todd Lipcon > Software Engineer, Cloudera > -- Todd Lipcon Software Engineer, Cloudera
