llvm dev - Mar 2016 - [Release-testers] [3.8 Release] RC3 has been tagged

On Mon, Feb 29, 2016 at 2:20 AM, Daniel Sanders
<Daniel.Sanders at imgtec.com> wrote:
> clang+llvm-3.8.0-rc3-x86_64-linux-gnu-debian8.tar.xz (sha1sum:
2dedc6136d7cfbac8348652c543887964d92393c)
>         Native: All ok
>         Cross compiling to MIPS: All ok
>
> clang+llvm-3.8.0-rc3-mips-linux-gnu.tar.xz (sha1sum:
f286149dbb2ea7e194c5c3719b6cded476f6e65f)
>         All ok (aside from non-regression failures in check-all).
>         There were two kinds of check-all failure:
>         * mips64 sanitizers. Not a regression since mip64 sanitizers
didn't ship in 3.7.1
>         * atomic tests fail due to missing -latomic on link. Not a
regression since _no_ libc++ tests ran in 3.7.1 (this was obscured by the -s on
llvm-lit).
>         Failing Tests (76):
>             AddressSanitizer-mips64-linux ::
TestCases/Posix/coverage-direct-activation.cc
>             AddressSanitizer-mips64-linux ::
TestCases/Posix/coverage-direct-large.cc
>             AddressSanitizer-mips64-linux ::
TestCases/Posix/coverage-direct.cc
>             AddressSanitizer-mips64-linux ::
TestCases/Posix/coverage-fork-direct.cc
>             AddressSanitizer-mips64-linux :: TestCases/Posix/coverage.cc
>             DataFlowSanitizer :: custom.cc
>             DataFlowSanitizer :: propagate.c
>             LeakSanitizer-AddressSanitizer :: TestCases/swapcontext.cc
>             LeakSanitizer-AddressSanitizer :: TestCases/use_registers.cc
>             LeakSanitizer-Standalone :: TestCases/swapcontext.cc
>             LeakSanitizer-Standalone :: TestCases/use_registers.cc
>             MemorySanitizer :: Linux/process_vm_readv.cc
>             MemorySanitizer :: allocator_mapping.cc
>             MemorySanitizer :: dlerror.cc
>             MemorySanitizer :: dtls_test.c
>             MemorySanitizer :: memcmp_test.cc
>             MemorySanitizer :: msan_print_shadow3.cc
>             MemorySanitizer :: param_tls_limit.cc
>             MemorySanitizer :: unaligned_read_origin.cc
>             MemorySanitizer-Unit ::
Msan-mips64-Test/MemorySanitizer.SmallPreAllocatedStackThread
>             MemorySanitizer-Unit ::
Msan-mips64-Test/MemorySanitizer.UnalignedLoad
>             MemorySanitizer-Unit ::
Msan-mips64-Test/MemorySanitizer.UnalignedStore16
>             MemorySanitizer-Unit ::
Msan-mips64-Test/MemorySanitizer.UnalignedStore16_precise
>             MemorySanitizer-Unit ::
Msan-mips64-Test/MemorySanitizer.UnalignedStore16_precise2
>             MemorySanitizer-Unit ::
Msan-mips64-Test/MemorySanitizer.UnalignedStore32
>             MemorySanitizer-Unit ::
Msan-mips64-Test/MemorySanitizer.gethostbyname_r_erange
>             MemorySanitizer-Unit ::
Msan-mips64-Test/MemorySanitizer.ptrtoint
>             MemorySanitizer-Unit :: Msan-mips64-Test/MemorySanitizer.shmat
>             MemorySanitizer-Unit ::
Msan-mips64-with-call-Test/MemorySanitizer.SmallPreAllocatedStackThread
>             MemorySanitizer-Unit ::
Msan-mips64-with-call-Test/MemorySanitizer.UnalignedLoad
>             MemorySanitizer-Unit ::
Msan-mips64-with-call-Test/MemorySanitizer.UnalignedStore16
>             MemorySanitizer-Unit ::
Msan-mips64-with-call-Test/MemorySanitizer.UnalignedStore16_precise
>             MemorySanitizer-Unit ::
Msan-mips64-with-call-Test/MemorySanitizer.UnalignedStore16_precise2
>             MemorySanitizer-Unit ::
Msan-mips64-with-call-Test/MemorySanitizer.UnalignedStore32
>             MemorySanitizer-Unit ::
Msan-mips64-with-call-Test/MemorySanitizer.gethostbyname_r_erange
>             MemorySanitizer-Unit ::
Msan-mips64-with-call-Test/MemorySanitizer.ptrtoint
>             SanitizerCommon-Unit ::
Sanitizer-mips64-Test/SanitizerCommon.FileOps
>             SanitizerCommon-Unit ::
Sanitizer-mips64-Test/SanitizerIoctl.KVM_GET_LAPIC
>             SanitizerCommon-Unit ::
Sanitizer-mips64-Test/SanitizerIoctl.KVM_GET_MP_STATE
>             SanitizerCommon-asan :: Linux/getpwnam_r_invalid_user.cc
>             SanitizerCommon-lsan :: Linux/getpwnam_r_invalid_user.cc
>             ThreadSanitizer-mips64 :: atexit2.cc
>             ThreadSanitizer-mips64 :: deadlock_detector_stress_test.cc
>             ThreadSanitizer-mips64 :: java_alloc.cc
>             ThreadSanitizer-mips64 :: java_race_pc.cc
>             ThreadSanitizer-mips64 :: longjmp.cc
>             ThreadSanitizer-mips64 :: longjmp2.cc
>             ThreadSanitizer-mips64 :: longjmp3.cc
>             ThreadSanitizer-mips64 :: longjmp4.cc
>             ThreadSanitizer-mips64 :: map32bit.cc
>             ThreadSanitizer-mips64 :: race_on_mutex.c
>             ThreadSanitizer-mips64 :: signal_longjmp.cc
>             libc++ :: std/atomics/atomics.types.generic/integral.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_compare_exchange_strong.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_compare_exchange_strong_explicit.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_compare_exchange_weak.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_compare_exchange_weak_explicit.pass.cpp
>            libc++ :: std/atomics/atomics.types.oper
>         1 warning(s) in tests.
>        
ations/atomics.types.operations.req/atomic_exchange_explicit.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_add.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_add_explicit.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_and.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_and_explicit.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_or.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_or_explicit.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_sub.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_sub_explicit.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_xor.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_xor_explicit.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_init.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_is_lock_free.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_load.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_load_explicit.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_store.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_store_explicit.pass.cpp
>             libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/ctor.pass.cpp
>
>           Expected Passes    : 31225
>           Expected Failures  : 211
>           Unsupported Tests  : 875
>           Unexpected Failures: 76
>
> clang+llvm-3.8.0-rc3-mipsel-linux-gnu.tar.xz
>         My machine died during the check-all stage and disappeared from the
network. I've fixed it and am currently running the last few bits of
test-release.sh manually.
Thanks, let me know how this turns out.

So far, it sounds like there are no new issues in rc3, so I'm hoping
we can make that the final version for 3.8.0 real soon.

Cheers,
Hans




> From: Release-testers [release-testers-bounces at lists.llvm.org] on behalf
of Hans Wennborg via Release-testers [release-testers at lists.llvm.org]
> Sent: 23 February 2016 21:51
> To: release-testers at lists.llvm.org
> Cc: llvm-dev; cfe-dev; openmp-dev (openmp-dev at lists.llvm.org); LLDB Dev
> Subject: [Release-testers] [3.8 Release] RC3 has been tagged
>
> Dear testers,
>
> Release Candidate 3 has just been tagged [1]. Please build, test, and
> upload to the sftp.
>
> If there are no regressions from previous release candidates, this
> will be the last release candidate before the final release.
>
> Release notes can still go into the branch.
>
> Thanks again for all your work!
> Hans
>
>  [1]
http://lists.llvm.org/pipermail/llvm-branch-commits/2016-February/009866.html
> _______________________________________________
> Release-testers mailing list
> Release-testers at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers

> > clang+llvm-3.8.0-rc3-mipsel-linux-gnu.tar.xz
> >         My machine died during the check-all stage and disappeared
from the
> network. I've fixed it and am currently running the last few bits of
test-
> release.sh manually.
> 
> Thanks, let me know how this turns out.
> 
> So far, it sounds like there are no new issues in rc3, so I'm hoping
> we can make that the final version for 3.8.0 real soon.
> 
> Cheers,
> Hans
> 
'check-all' is still killing the machine but I think I know what the
problem is. While investigating some of the rc2 problems I noticed that
g++-multilib wasn't installed and this was disabling the mips64el
sanitizers. Installing this didn't cause problems at the time but I've
noticed that some of the mips64el sanitizer tests are very memory hungry. I
noticed several occasions where parallel asan tests were consuming ~200% of RAM
and it would have been swapping heavily (on a USB2 disk) to cope. If later tests
require even more RAM then it would explain why the system stops responding.
I'm going to uninstall g++-multilib and rebuild rc3. Hopefully that will
make check-all work again.

For now, I've commented out the check-all command and uploaded
clang+llvm-3.8.0-rc3-mipsel-linux-gnu.tar.xz (sha1sum:
e280bf6db094a81f22f4cdf6c0b5955493a11b05). I'm going to run this through my
usual test-suites and I should have the results by this evening.

> > > clang+llvm-3.8.0-rc3-mipsel-linux-gnu.tar.xz
> > >         My machine died during the check-all stage and
disappeared from the
> > network. I've fixed it and am currently running the last few bits
of test-
> > release.sh manually.
> >
> > Thanks, let me know how this turns out.
> >
> > So far, it sounds like there are no new issues in rc3, so I'm
hoping
> > we can make that the final version for 3.8.0 real soon.
> >
> > Cheers,
> > Hans
> >
> 
> 'check-all' is still killing the machine but I think I know what
the problem is. While investigating some of the rc2
> problems I noticed that g++-multilib wasn't installed and this was
disabling the mips64el sanitizers. Installing this
> didn't cause problems at the time but I've noticed that some of the
mips64el sanitizer tests are very memory hungry.
> I noticed several occasions where parallel asan tests were consuming ~200%
of RAM and it would have been
> swapping heavily (on a USB2 disk) to cope. If later tests require even more
RAM then it would explain why the
> system stops responding. I'm going to uninstall g++-multilib and
rebuild rc3. Hopefully that will make check-all work
> again.
It seems there's was still just enough multilib support on the machine to
trigger mips64el sanitizers again but having worked around that the parts of lit
that aren't mips64el sanitizers are working so far. llvm-lit is still going
but big-endian mips and cross compilation was fine so I'm expecting little
endian to be ok too. It's showing an ETA of about 90 mins for the remaining
tests from clang and llvm at the moment. I'm going to run the MIPS32
sanitizer lit tests after that.

Overall, I think we're probably ready for final. I just can't confirm
that rc3 was definitely ok for little endian mips yet.
> For now, I've commented out the check-all command and uploaded
clang+llvm-3.8.0-rc3-mipsel-linux-gnu.tar.xz
> (sha1sum: e280bf6db094a81f22f4cdf6c0b5955493a11b05). I'm going to run
this through my usual test-suites and I
> should have the results by this evening.
The LNT test-suite runs were ok with the rc3 build.