<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font face="monospace">Uploaded Ubuntu 21.04 with lldb.<br>
<br>
sha256sum
clang+llvm-12.0.1-rc2-x86_64-linux-gnu-ubuntu-21.04.tar.xz<br>
0cc0ad5c2952400dd3d795f11cdcd03569b8060f97771e5f7c7e4b0f5738c897<br>
<br>
Failed Tests (14):<br>
MemorySanitizer-Unit ::
./Msan-x86_64-Test/MemorySanitizer.fstatat<br>
MemorySanitizer-Unit ::
./Msan-x86_64-Test/MemorySanitizer.stat<br>
MemorySanitizer-Unit ::
./Msan-x86_64-with-call-Test/MemorySanitizer.fstatat<br>
MemorySanitizer-Unit ::
./Msan-x86_64-with-call-Test/MemorySanitizer.stat<br>
MemorySanitizer-X86_64 :: fstat.cpp<br>
MemorySanitizer-lld-X86_64 :: fstat.cpp<br>
SanitizerCommon-asan-i386-Linux :: Linux/crypt_r.cpp<br>
SanitizerCommon-asan-i386-Linux :: Posix/crypt.cpp<br>
SanitizerCommon-lsan-i386-Linux :: Linux/crypt_r.cpp<br>
SanitizerCommon-lsan-i386-Linux :: Posix/crypt.cpp<br>
SanitizerCommon-msan-x86_64-Linux :: Posix/lstat.cpp<br>
SanitizerCommon-ubsan-i386-Linux :: Linux/crypt_r.cpp<br>
SanitizerCommon-ubsan-i386-Linux :: Posix/crypt.cpp<br>
lldb-api ::
tools/lldb-vscode/runInTerminal/TestVSCode_runInTerminal.py<br>
<br>
<br>
Testing Time: 526.84s<br>
Unsupported : 3416<br>
Passed : 84243<br>
Expectedly Failed: 267<br>
Failed : 14<br>
<br>
<br>
All failed tests covered by prior bugs.<br>
Bug 50487 - TEST 'MemorySanitizer-Unit ::
./Msan-x86_64-Test/MemorySanitizer.fstatat' FAILED<br>
Bug 50488 - TEST 'MemorySanitizer-Unit ::
./Msan-x86_64-Test/MemorySanitizer.stat' FAILED<br>
Bug 50489 - TEST 'MemorySanitizer-Unit ::
./Msan-x86_64-with-call-Test/MemorySanitizer.fstatat' FAILED<br>
Bug 50490 - TEST 'MemorySanitizer-Unit ::
./Msan-x86_64-with-call-Test/MemorySanitizer.stat' FAILED<br>
Bug 50491 - TEST 'MemorySanitizer-X86_64 :: fstat.cpp' FAILED<br>
Bug 50492 - TEST 'MemorySanitizer-lld-X86_64 :: fstat.cpp'
FAILED<br>
48946 - skipping incompatible
/usr/lib/x86_64-linux-gnu/libcrypt.so when searching for -lcrypt<br>
48960 - FAIL: lldb-api ::
tools/lldb-vscode/runInTerminal/TestVSCode_runInTerminal.py<br>
<br>
llvm-test-suite<br>
Passed: 2405<br>
<br>
../utils/compare.py results.json<br>
Tests: 2825<br>
Metric: exec_time<br>
<br>
Program 12.0.1-rc1
12.0.1-rc2 diff <br>
test-suite...d_ops_test_op_pcmpgtd_164.test 0.00
0.00 inf%<br>
test-suite...te/GCC-C-execute-pr28982a.test 0.00
0.00 inf%<br>
test-suite...ute/GCC-C-execute-pr44575.test 0.00
0.00 inf%<br>
test-suite...ssion-C++-class_hierarchy.test 0.00
0.00 inf%<br>
test-suite...ests/2002-05-02-CastTest2.test 0.00
0.00 inf%<br>
test-suite...te/GCC-C-execute-920829-1.test 0.00
0.00 inf%<br>
test-suite...d_ops_test_op_vpmaxud_396.test 0.00
0.01 inf%<br>
test-suite...ssion-C++-ConditionalExpr.test 0.00
0.00 inf%<br>
test-suite.../GCC-C-execute-20001031-1.test 0.00
0.00 inf%<br>
test-suite...md_ops_test_op_pcmpeqd_67.test 0.00
0.00 inf%<br>
test-suite...urce/Applications/hbd/hbd.test 0.00
0.00 inf%<br>
test-suite...ecute/GCC-C-execute-ffs-1.test 0.00
0.00 inf%<br>
test-suite...ear-algebra/solvers/lu/lu.test 0.00
0.00 inf%<br>
test-suite...e/GCC-C-execute-pr20621-1.test 0.00
0.00 inf%<br>
test-suite...e/GCC-C-execute-wchar_t-1.test 0.00
0.00 inf%<br>
Geomean
difference
nan%<br>
12.0.1-rc1 12.0.1-rc2 diff<br>
count 2807.000000 2807.000000 2785.000000<br>
mean 223.561162 235.984152 inf <br>
std 2825.553821 3375.282608 NaN <br>
min 0.000000 0.000000 -1.000000 <br>
25% 0.000400 0.000400 -0.152174 <br>
50% 0.000500 0.000500 0.000000 <br>
75% 0.011150 0.011650 0.250000 <br>
max 85835.460625 110222.932000 inf </font></p>
<p><font face="monospace">Neil Nelson</font><br>
</p>
<div class="moz-cite-prefix"><font size="-1">On 6/17/21 12:53 AM,
Tom Stellard via llvm-dev wrote:<br>
</font></div>
<blockquote type="cite"
cite="mid:13498d82-98b6-5bcc-0104-55ffbab0503d@redhat.com"><font
size="-1">Hi,
<br>
<br>
I've tagged the 12.0.1-rc2 release, so testers may begin testing
and uploading
<br>
binaries.
<br>
<br>
There are still a few fixes working their way through the
process, so there
<br>
will be another release candidate. If you submitted a backport
request
<br>
before last Friday's deadline then it should make it in to the
final release
<br>
unless a reviewer rejects it or there is a problem discovered
with the fix.
<br>
My plan is to do -rc3 once all these fixes are merged.
<br>
<br>
I am also going to continue accepting new backport requests up
until
<br>
-rc3 is tagged (goal for -rc3 is next Tuesday). However, I will
not be
<br>
delaying -rc3 for any fixes submitted after Friday unless they
are critical.
<br>
<br>
If you still have fixes and want to increase the chances of
getting them into
<br>
the release, please make sure the fix applies cleanly to the
release/12.x
<br>
and passes all the lit tests. If it doesn't then please
manually backport
<br>
it, fix all the issues and post a patch or git branch in
bugzilla. It is also
<br>
helpful if you cc either the patch author, patch reviewer, or
code owner for
<br>
the fix and ask their opinion on backporting it.
<br>
<br>
Thanks,
<br>
Tom
<br>
<br>
_______________________________________________
<br>
LLVM Developers mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a>
</font><br>
</blockquote>
</body>
</html>