[lldb-dev] [cfe-dev] [LLVMdev] [3.7 Release] RC1 has been tagged, Testing Phase I begins

[Hans Wennborg]

On Tue, Jul 21, 2015 at 7:39 AM, Ben Pope <benpope81 at gmail.com> wrote:
> On Tuesday, July 21, 2015 05:51 AM, Hans Wennborg wrote:
>>
>> I don't think the test failures are correlated to not getting a
>> tarball. It's probably the "rpath problem" that Dimitry mentioned
>> further up in the thread. Try using his patch for it
>
>
> It still failed, I used test-release.sh r242767 which appears to have the
> rpath change.

Weird. Did you get any output suggesting what the error was?

>> or disabling -o pipefail.
>
>
> That sort of worked. Again, the paths in the install directory are
> ./usr/local/ but in the tarball they seem as before.

Having /usr/local in the install directory during the build is
expected. As long as they don't up in the tarball (and I fixed that),
it's fine.

> Also, cxxabi.h is in
> ./include/c++/v1 which is nice, but no unwind.h, I haven't checked if that's
> a problem yet.

I'm not that familiar with libunwind. Clang should have installed an
unwind.h in lib/clang/3.7.0/include/unwind.h. I don't know if
libunwind is expected to install another one.

> Failing Tests (9):
>     MemorySanitizer :: Linux/tcgetattr.cc
>     MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent
>     MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent_r
>     MemorySanitizer-Unit ::
> Msan-x86_64-with-call-Test/MemorySanitizer.getmntent
>     MemorySanitizer-Unit ::
> Msan-x86_64-with-call-Test/MemorySanitizer.getmntent_r
>     SanitizerCommon-asan :: Linux/getpass.cc
>     SanitizerCommon-lsan :: Linux/getpass.cc
>     SanitizerCommon-msan :: Linux/getpass.cc
>     SanitizerCommon-tsan :: Linux/getpass.cc
>
>   Expected Passes    : 24015
>   Expected Failures  : 131
>   Unsupported Tests  : 377
>   Unexpected Failures: 9
>
> Full output below.
>
> lnt seems fine, I've uploaded this file:
> clang+llvm-3.7.0-rc1-x86_64-linux-gnu-ubuntu-15.04.tar.xz
>
>> And please see if you can dig out some more details about the failing
>> tests and get bugs filed.
>
>
> I don't really know what I'm looking for, if you need more info I'm happy to
> provide it.

The output below is great. I'll try to get these investigated.

Thanks,
Hans