Hans Wennborg via llvm-dev
2016-Feb-23 21:51 UTC
[llvm-dev] [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
Ben Pope via llvm-dev
2016-Feb-24 04:51 UTC
[llvm-dev] [Release-testers] [3.8 Release] RC3 has been tagged
On Wednesday, February 24, 2016 05:51 AM, Hans Wennborg via Release-testers wrote:> Dear testers, > > Release Candidate 3 has just been tagged [1]. Please build, test, and > upload to the sftp.On Ubuntu 15.10 x86_64 I got: Failing Tests (2): MemorySanitizer :: Linux/forkpty.cc MemorySanitizer :: Linux/tcgetattr.cc Expected Passes : 31860 Expected Failures : 209 Unsupported Tests : 648 Unexpected Failures: 2 With RC2 there were no failures, but it looks like 15 tests have been added. Ben
Hans Wennborg via llvm-dev
2016-Feb-24 18:24 UTC
[llvm-dev] [3.8 Release] RC3 has been tagged
On Tue, Feb 23, 2016 at 1:51 PM, Hans Wennborg <hans at chromium.org> wrote:> Release Candidate 3 has just been tagged [1]. Please build, test, and > upload to the sftp.Windows (sha1): 76f8f91debd2e101b9adc4a6f2230fcd5e18bb5c LLVM-3.8.0-rc3-win32.exe b87654327d3ae537f8afec06ea0fa63121b9a86e LLVM-3.8.0-rc3-win64.exe - Hans
Hans Wennborg via llvm-dev
2016-Feb-24 18:33 UTC
[llvm-dev] [Release-testers] [3.8 Release] RC3 has been tagged
On Tue, Feb 23, 2016 at 8:51 PM, Ben Pope <benpope81 at gmail.com> wrote:> On Wednesday, February 24, 2016 05:51 AM, Hans Wennborg via Release-testers > wrote: >> >> Dear testers, >> >> Release Candidate 3 has just been tagged [1]. Please build, test, and >> upload to the sftp. > > > On Ubuntu 15.10 x86_64 I got: > > Failing Tests (2): > MemorySanitizer :: Linux/forkpty.cc > MemorySanitizer :: Linux/tcgetattr.cc > > Expected Passes : 31860 > Expected Failures : 209 > Unsupported Tests : 648 > Unexpected Failures: 2 > > With RC2 there were no failures, but it looks like 15 tests have been added.Hmm, those two tests are not new, but maybe something changed that made them run now and not before. Perhaps related to r261162? In any case, I'm not too worried about these failures, they probably just didn't run before. Thanks, Hans
Renato Golin via llvm-dev
2016-Feb-24 18:52 UTC
[llvm-dev] [cfe-dev] [3.8 Release] RC3 has been tagged
On 23 February 2016 at 21:51, Hans Wennborg via cfe-dev <cfe-dev at lists.llvm.org> wrote:> Dear testers, > > Release Candidate 3 has just been tagged [1]. Please build, test, and > upload to the sftp.Uploaded and tested for ARM and AArch64, all good. Remember, this is *not* using a new Linux, so the GCC 5 issue doesn't apply. I'm hoping we fix the issue for 3.9, so that I can update our machine and test newer system behaviour. cheers, --renato
Dimitry Andric via llvm-dev
2016-Feb-24 19:18 UTC
[llvm-dev] [Release-testers] [3.8 Release] RC3 has been tagged
On 23 Feb 2016, at 22:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote:> > Release Candidate 3 has just been tagged [1]. Please build, test, and > upload to the sftp.Built and tested just fine on FreeBSD 10. Uploaded the following tarballs: SHA256 (clang+llvm-3.8.0-rc3-amd64-unknown-freebsd10.tar.xz) = 0ac847a23b881d27883b83add8926fff8265b650ef6fbf49bae3fc145305399a SHA256 (clang+llvm-3.8.0-rc3-i386-unknown-freebsd10.tar.xz) = 91a0f3c108f9baa9e0f374931f2efa1b1e2413b0ae3a6217fb8bf4111c5c4adb -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/20160224/bdc11163/attachment.sig>
Ben Pope via llvm-dev
2016-Feb-25 05:11 UTC
[llvm-dev] [Release-testers] [3.8 Release] RC3 has been tagged
On Wednesday, February 24, 2016 05:51 AM, Hans Wennborg via Release-testers wrote:> Dear testers, > > Release Candidate 3 has just been tagged [1]. Please build, test, and > upload to the sftp.Uploaded: clang+llvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-16.04.tar.xz clang+llvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-15.10.tar.xz clang+llvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-14.04.tar.xz On Ubuntu 16.04 x86_64: Failing Tests (7): MemorySanitizer :: Linux/forkpty.cc 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 Profile :: instrprof-error.c Expected Passes : 31128 Expected Failures : 172 Unsupported Tests : 615 Unexpected Failures: 7 On Ubuntu 15.10 x86_64: Failing Tests (2): MemorySanitizer :: Linux/forkpty.cc MemorySanitizer :: Linux/tcgetattr.cc Expected Passes : 31860 Expected Failures : 209 Unsupported Tests : 648 Unexpected Failures: 2 On Ubuntu 14.04 x86_64: Failing Tests (9): MemorySanitizer :: Linux/forkpty.cc 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 Profile :: instrprof-error.c libc++ :: std/localization/locale.categories/category.ctype/locale.ctype.byname/types.pass.cpp libc++ :: std/localization/locales/locale/locale.cons/char_pointer.pass.cpp Expected Passes : 31194 Expected Failures : 195 Unsupported Tests : 526 Unexpected Failures: 9 LNT results look good, although they are, perhaps 20% slower than most of my previous runs. Ben
Nikola Smiljanic via llvm-dev
2016-Feb-25 20:36 UTC
[llvm-dev] [Release-testers] [3.8 Release] RC3 has been tagged
Uploaded Fedora and openSUSE binaries. Looking good. On Thu, Feb 25, 2016 at 4:11 PM, Ben Pope via Release-testers < release-testers at lists.llvm.org> wrote:> On Wednesday, February 24, 2016 05:51 AM, Hans Wennborg via > Release-testers wrote: > >> Dear testers, >> >> Release Candidate 3 has just been tagged [1]. Please build, test, and >> upload to the sftp. >> > Uploaded: > clang+llvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-16.04.tar.xz > clang+llvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-15.10.tar.xz > clang+llvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-14.04.tar.xz > > On Ubuntu 16.04 x86_64: > > Failing Tests (7): > MemorySanitizer :: Linux/forkpty.cc > 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 > Profile :: instrprof-error.c > > Expected Passes : 31128 > Expected Failures : 172 > Unsupported Tests : 615 > Unexpected Failures: 7 > > > On Ubuntu 15.10 x86_64: > > Failing Tests (2): > MemorySanitizer :: Linux/forkpty.cc > MemorySanitizer :: Linux/tcgetattr.cc > > Expected Passes : 31860 > Expected Failures : 209 > Unsupported Tests : 648 > Unexpected Failures: 2 > > > On Ubuntu 14.04 x86_64: > > Failing Tests (9): > MemorySanitizer :: Linux/forkpty.cc > 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 > Profile :: instrprof-error.c > libc++ :: > std/localization/locale.categories/category.ctype/locale.ctype.byname/types.pass.cpp > libc++ :: > std/localization/locales/locale/locale.cons/char_pointer.pass.cpp > > Expected Passes : 31194 > Expected Failures : 195 > Unsupported Tests : 526 > Unexpected Failures: 9 > > LNT results look good, although they are, perhaps 20% slower than most of > my previous runs. > > Ben > > _______________________________________________ > Release-testers mailing list > Release-testers at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160226/d158f916/attachment.html>
Brian Cain via llvm-dev
2016-Feb-27 05:29 UTC
[llvm-dev] [Release-testers] [3.8 Release] RC3 has been tagged
Uploaded clang+llvm-3.8.0-rc3-linux-x86_64-sles11.3.tar.xz and clang+llvm-3.8.0-rc3-linux-armhf-vivid.tar.xz f8f8b0ff8f9709cbf63097727a96fde5054efefe rc3/clang+llvm-3.8.0-rc3-linux-x86_64-sles11.3.tar.xz 9202d52a9bff5464d0b76750c41ffec0d7d99c17 rc3/clang+llvm-3.8.0-rc3-linux-armhf-vivid.tar.xz No new unexpected failures for each. On Tue, Feb 23, 2016 at 3:51 PM, Hans Wennborg via Release-testers < release-testers at lists.llvm.org> wrote:> 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 >-- -Brian -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160226/7362f3ce/attachment.html>
Daniel Sanders via llvm-dev
2016-Feb-29 10:20 UTC
[llvm-dev] [Release-testers] [3.8 Release] RC3 has been tagged
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. ________________________________________ 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
Hans Wennborg via llvm-dev
2016-Mar-01 02:59 UTC
[llvm-dev] [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
Possibly Parallel Threads
- [Release-testers] [3.8 Release] RC3 has been tagged
- [LLVMdev] [3.7 Release] RC2 has been tagged, Testing Phase II begins
- [LLVMdev] [cfe-dev] [3.7 Release] RC1 has been tagged, Testing Phase I begins
- [LLVMdev] [3.7 Release] RC2 has been tagged, Testing Phase II begins
- [cfe-dev] [3.8 Release] RC1 has been tagged