Tom Stellard via llvm-dev
2021-Jun-17 06:53 UTC
[llvm-dev] Release 12.0.1-rc2 tagged + extended deadline for requesting backports
Hi, I've tagged the 12.0.1-rc2 release, so testers may begin testing and uploading binaries. There are still a few fixes working their way through the process, so there will be another release candidate. If you submitted a backport request before last Friday's deadline then it should make it in to the final release unless a reviewer rejects it or there is a problem discovered with the fix. My plan is to do -rc3 once all these fixes are merged. I am also going to continue accepting new backport requests up until -rc3 is tagged (goal for -rc3 is next Tuesday). However, I will not be delaying -rc3 for any fixes submitted after Friday unless they are critical. If you still have fixes and want to increase the chances of getting them into the release, please make sure the fix applies cleanly to the release/12.x and passes all the lit tests. If it doesn't then please manually backport it, fix all the issues and post a patch or git branch in bugzilla. It is also helpful if you cc either the patch author, patch reviewer, or code owner for the fix and ask their opinion on backporting it. Thanks, Tom
Neil Nelson via llvm-dev
2021-Jun-17 16:54 UTC
[llvm-dev] Release 12.0.1-rc2 tagged + extended deadline for requesting backports
Uploaded Ubuntu 21.04 with lldb. sha256sum clang+llvm-12.0.1-rc2-x86_64-linux-gnu-ubuntu-21.04.tar.xz 0cc0ad5c2952400dd3d795f11cdcd03569b8060f97771e5f7c7e4b0f5738c897 Failed Tests (14): MemorySanitizer-Unit :: ./Msan-x86_64-Test/MemorySanitizer.fstatat MemorySanitizer-Unit :: ./Msan-x86_64-Test/MemorySanitizer.stat MemorySanitizer-Unit :: ./Msan-x86_64-with-call-Test/MemorySanitizer.fstatat MemorySanitizer-Unit :: ./Msan-x86_64-with-call-Test/MemorySanitizer.stat MemorySanitizer-X86_64 :: fstat.cpp MemorySanitizer-lld-X86_64 :: fstat.cpp SanitizerCommon-asan-i386-Linux :: Linux/crypt_r.cpp SanitizerCommon-asan-i386-Linux :: Posix/crypt.cpp SanitizerCommon-lsan-i386-Linux :: Linux/crypt_r.cpp SanitizerCommon-lsan-i386-Linux :: Posix/crypt.cpp SanitizerCommon-msan-x86_64-Linux :: Posix/lstat.cpp SanitizerCommon-ubsan-i386-Linux :: Linux/crypt_r.cpp SanitizerCommon-ubsan-i386-Linux :: Posix/crypt.cpp lldb-api :: tools/lldb-vscode/runInTerminal/TestVSCode_runInTerminal.py Testing Time: 526.84s Unsupported : 3416 Passed : 84243 Expectedly Failed: 267 Failed : 14 All failed tests covered by prior bugs. Bug 50487 - TEST 'MemorySanitizer-Unit :: ./Msan-x86_64-Test/MemorySanitizer.fstatat' FAILED Bug 50488 - TEST 'MemorySanitizer-Unit :: ./Msan-x86_64-Test/MemorySanitizer.stat' FAILED Bug 50489 - TEST 'MemorySanitizer-Unit :: ./Msan-x86_64-with-call-Test/MemorySanitizer.fstatat' FAILED Bug 50490 - TEST 'MemorySanitizer-Unit :: ./Msan-x86_64-with-call-Test/MemorySanitizer.stat' FAILED Bug 50491 - TEST 'MemorySanitizer-X86_64 :: fstat.cpp' FAILED Bug 50492 - TEST 'MemorySanitizer-lld-X86_64 :: fstat.cpp' FAILED 48946 - skipping incompatible /usr/lib/x86_64-linux-gnu/libcrypt.so when searching for -lcrypt 48960 - FAIL: lldb-api :: tools/lldb-vscode/runInTerminal/TestVSCode_runInTerminal.py llvm-test-suite Passed: 2405 ../utils/compare.py results.json Tests: 2825 Metric: exec_time Program 12.0.1-rc1 12.0.1-rc2 diff test-suite...d_ops_test_op_pcmpgtd_164.test 0.00 0.00 inf% test-suite...te/GCC-C-execute-pr28982a.test 0.00 0.00 inf% test-suite...ute/GCC-C-execute-pr44575.test 0.00 0.00 inf% test-suite...ssion-C++-class_hierarchy.test 0.00 0.00 inf% test-suite...ests/2002-05-02-CastTest2.test 0.00 0.00 inf% test-suite...te/GCC-C-execute-920829-1.test 0.00 0.00 inf% test-suite...d_ops_test_op_vpmaxud_396.test 0.00 0.01 inf% test-suite...ssion-C++-ConditionalExpr.test 0.00 0.00 inf% test-suite.../GCC-C-execute-20001031-1.test 0.00 0.00 inf% test-suite...md_ops_test_op_pcmpeqd_67.test 0.00 0.00 inf% test-suite...urce/Applications/hbd/hbd.test 0.00 0.00 inf% test-suite...ecute/GCC-C-execute-ffs-1.test 0.00 0.00 inf% test-suite...ear-algebra/solvers/lu/lu.test 0.00 0.00 inf% test-suite...e/GCC-C-execute-pr20621-1.test 0.00 0.00 inf% test-suite...e/GCC-C-execute-wchar_t-1.test 0.00 0.00 inf% Geomean difference nan% 12.0.1-rc1 12.0.1-rc2 diff count 2807.000000 2807.000000 2785.000000 mean 223.561162 235.984152 inf std 2825.553821 3375.282608 NaN min 0.000000 0.000000 -1.000000 25% 0.000400 0.000400 -0.152174 50% 0.000500 0.000500 0.000000 75% 0.011150 0.011650 0.250000 max 85835.460625 110222.932000 inf Neil Nelson On 6/17/21 12:53 AM, Tom Stellard via llvm-dev wrote:> Hi, > > I've tagged the 12.0.1-rc2 release, so testers may begin testing and > uploading > binaries. > > There are still a few fixes working their way through the process, so > there > will be another release candidate. If you submitted a backport request > before last Friday's deadline then it should make it in to the final > release > unless a reviewer rejects it or there is a problem discovered with the > fix. > My plan is to do -rc3 once all these fixes are merged. > > I am also going to continue accepting new backport requests up until > -rc3 is tagged (goal for -rc3 is next Tuesday). However, I will not be > delaying -rc3 for any fixes submitted after Friday unless they are > critical. > > If you still have fixes and want to increase the chances of getting > them into > the release, please make sure the fix applies cleanly to the release/12.x > and passes all the lit tests. If it doesn't then please manually > backport > it, fix all the issues and post a patch or git branch in bugzilla. It > is also > helpful if you cc either the patch author, patch reviewer, or code > owner for > the fix and ask their opinion on backporting it. > > Thanks, > Tom > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210617/3bfe4274/attachment.html>
Yvan Roux via llvm-dev
2021-Jun-21 13:55 UTC
[llvm-dev] Release 12.0.1-rc2 tagged + extended deadline for requesting backports
Hi no issues for AArch64 and ARM binaries (despite the known CFI ones observed on 32-bit). Binaries uploaded sha256sum: 25a49150c3a7bc9d14bebf57479113a6d08a54c70f770ed90d6a5c4f clang+llvm-12.0.1-rc2-aarch64-linux-gnu.tar.xz 5b841423368543084f14f10c49ebdc7517f19391ede56d0c0a40a88a clang+llvm-12.0.1-rc2-armv7a-linux-gnueabihf.tar.xz Cheers, Yvan On Thu, 17 Jun 2021 at 08:53, Tom Stellard via llvm-dev < llvm-dev at lists.llvm.org> wrote:> Hi, > > I've tagged the 12.0.1-rc2 release, so testers may begin testing and > uploading > binaries. > > There are still a few fixes working their way through the process, so there > will be another release candidate. If you submitted a backport request > before last Friday's deadline then it should make it in to the final > release > unless a reviewer rejects it or there is a problem discovered with the fix. > My plan is to do -rc3 once all these fixes are merged. > > I am also going to continue accepting new backport requests up until > -rc3 is tagged (goal for -rc3 is next Tuesday). However, I will not be > delaying -rc3 for any fixes submitted after Friday unless they are > critical. > > If you still have fixes and want to increase the chances of getting them > into > the release, please make sure the fix applies cleanly to the release/12.x > and passes all the lit tests. If it doesn't then please manually backport > it, fix all the issues and post a patch or git branch in bugzilla. It is > also > helpful if you cc either the patch author, patch reviewer, or code owner > for > the fix and ask their opinion on backporting it. > > Thanks, > Tom > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210621/66b2dd9c/attachment.html>
Albion Fung via llvm-dev
2021-Jun-21 17:50 UTC
[llvm-dev] Release 12.0.1-rc2 tagged + extended deadline for requesting backports
Hello, SHA1 for PowerPC - Ubuntu: 847b49fa2937e000ad440f3bf7daa83511de305f clang+llvm-12.0.1-rc2-powerpc64le-linux-ubuntu-18.04.tar.xz - RHEL: 7ff95aa59fe77fe85326b26ff18c52e0cda71135 clang+llvm-12.0.1-rc2-powerpc64le-linux-rhel-7.4.tar.xz Thanks, Albion On Thu, 17 Jun 2021 at 02:53, Tom Stellard via llvm-dev < llvm-dev at lists.llvm.org> wrote:> Hi, > > I've tagged the 12.0.1-rc2 release, so testers may begin testing and > uploading > binaries. > > There are still a few fixes working their way through the process, so there > will be another release candidate. If you submitted a backport request > before last Friday's deadline then it should make it in to the final > release > unless a reviewer rejects it or there is a problem discovered with the fix. > My plan is to do -rc3 once all these fixes are merged. > > I am also going to continue accepting new backport requests up until > -rc3 is tagged (goal for -rc3 is next Tuesday). However, I will not be > delaying -rc3 for any fixes submitted after Friday unless they are > critical. > > If you still have fixes and want to increase the chances of getting them > into > the release, please make sure the fix applies cleanly to the release/12.x > and passes all the lit tests. If it doesn't then please manually backport > it, fix all the issues and post a patch or git branch in bugzilla. It is > also > helpful if you cc either the patch author, patch reviewer, or code owner > for > the fix and ask their opinion on backporting it. > > Thanks, > Tom > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210621/e900a4b1/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: clang+llvm-12.0.1-rc2-powerpc64le-linux-ubuntu-18.04.sha1 Type: application/octet-stream Size: 102 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210621/e900a4b1/attachment.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: clang+llvm-12.0.1-rc2-powerpc64le-linux-rhel-7.4.sha1 Type: application/octet-stream Size: 98 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210621/e900a4b1/attachment-0001.obj>
Dimitry Andric via llvm-dev
2021-Jun-26 08:08 UTC
[llvm-dev] [Release-testers] Release 12.0.1-rc2 tagged + extended deadline for requesting backports
On 17 Jun 2021, at 08:53, Tom Stellard via Release-testers <release-testers at lists.llvm.org> wrote:> > I've tagged the 12.0.1-rc2 release, so testers may begin testing and uploading > binaries.For 12.0.1 rc2, I have built and tested on both FreeBSD 11 and 12. No additional patches were needed. Main results on amd64-freebsd11: Unsupported : 5562 (rc1: 5562) Passed : 80200 (rc1: 80189) Expectedly Failed : 247 (rc1: 247) Timed Out : 1 (rc1: 2) Failed : 96 (rc1: 97) Unexpectedly Passed: 2 (rc1: 2) Test suite results on amd64-freebsd11: Passed: 2399 (rc1: 2399) Failed: 3 (rc1: 3) Main results on amd64-freebsd12: Unsupported : 5562 (rc1: 5562) Passed : 80202 (rc1: 80194) Expectedly Failed : 243 (rc1: 243) Timed Out : 3 (rc1: 2) Failed : 92 (rc1: 92) Unexpectedly Passed: 6 (rc1: 6) Test suite results on amd64-freebsd12: Passed: 2399 (rc1: 2399) Failed: 3 (rc1: 3) Main results on i386-freebsd11: Unsupported : 3976 (rc1: 3976) Passed : 76743 (rc1: 76736) Expectedly Failed : 224 (rc1: 224) Timed Out : 1 (rc1: 0) Failed : 54 (rc1: 53) Unexpectedly Passed: 1 (rc1: 1) Main results on i386-freebsd12: Unsupported : 3976 (rc1: 3976) Passed : 76747 (rc1: 76739) Expectedly Failed : 222 (rc1: 222) Failed : 51 (rc1: 50) Unexpectedly Passed: 3 (rc1: 3) Uploaded: SHA256 (clang+llvm-12.0.1-rc2-amd64-unknown-freebsd11.tar.xz) = 1b9f9e1924307adcba85085f7f90a63a87d46bcd53caea5406d755977040f8c0 SHA256 (clang+llvm-12.0.1-rc2-amd64-unknown-freebsd12.tar.xz) = bcdadf59384d910938fa752bcfa89d9bd9683d63f94280181cb726c92e0d74d8 SHA256 (clang+llvm-12.0.1-rc2-i386-unknown-freebsd11.tar.xz) = 9c55ca566b4bad83993e52c6598eca1c8a201fb962583e692622d7a1d672e932 SHA256 (clang+llvm-12.0.1-rc2-i386-unknown-freebsd12.tar.xz) = be1606a3a8a696868455fa9c9458c938d4fda3e4364278d635971ae2e79befda -Dimitry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 223 bytes Desc: Message signed with OpenPGP URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210626/d2c0a520/attachment.sig>