[llvm-dev] [Release-testers] [3.9 Release] Release Candidate 1 has been tagged

Wed Aug 3 11:24:54 PDT 2016

On 30 Jul 2016, at 00:57, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote:
> 
> 3.9.0-rc1 was just tagged from the 3.9 branch at r277207.

After fixing two compiler-rt test failures (see r277297 and r277300) and one openmp test link failure (see https://reviews.llvm.org/D23084), I'm left with only two failing tests:

Failing Tests (2):
    ThreadSanitizer-x86_64 :: inlined_memcpy_race2.cc
    ThreadSanitizer-x86_64 :: signal_reset.cc

  Expected Passes    : 28511
  Expected Failures  : 155
  Unsupported Tests  : 1080
  Unexpected Failures: 2

These both fail because they hang indefinitely, and have to be killed for check-all to continue.

Unfortunately this is in TSan, which does not work at all on FreeBSD 11 and higher, due to a conflict of initialization order with our jemalloc.  So I am not extremely keen on fixing this before the release.

I uploaded the following:

SHA256 (clang+llvm-3.9.0-rc1-amd64-unknown-freebsd10.tar.xz) = 8d3b1d50c00901d235c110a84afa5c16f0e80683928a47e31f8c189a41268698
SHA256 (clang+llvm-3.9.0-rc1-i386-unknown-freebsd10.tar.xz) = 602373772b4ff2fc70c97f5483db33e3ecfd24122aed96d6fe083bae3ea0e6f6

For i386 and amd64, this contains llvm, clang, compiler-rt and lldb, while on amd64 there is also openmp.  We cannot yet build libc++, libcxxabi and libunwind, due to some missing functionality in our system unwinder.  Maybe if test-release.sh supported building libc++ separately, I could add it for the next RC.

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160803/73508c37/attachment.sig>