[Release-testers] [cfe-dev] [llvm-dev] [11.0.0 Release] Release Candidate 6 is here
Diana Picus via Release-testers
release-testers at lists.llvm.org
Mon Oct 12 01:27:15 PDT 2020
Uploaded Arm & AArch64:
Same as previous rc's.
On Sat, 10 Oct 2020 at 04:46, Shoaib Meenai via cfe-dev
<cfe-dev at lists.llvm.org> wrote:
> Uploaded macOS binaries to https://drive.google.com/file/d/1OVsImFG99a0jNOWc1IDhRvER3CvbGmFp/view?usp=sharing.
> The SHA-256 is:
> b35f3b6ce4de703f015bdf9d936f530b28c752737c2dd60715bd3d098787652b clang+llvm-11.0.0-rc6-x86_64-apple-darwin.tar.xz
> The full test results are:
> Failed Tests (2):
> libunwind :: libunwind_01.pass.cpp
> libunwind :: signal_frame.pass.cpp
> Testing Time: 3211.12s
> Unsupported : 3200
> Passed : 68254
> Expectedly Failed: 264
> Failed : 2
> The libunwind tests failed with rc5 and also fail for 10.0.1 on my machine, so it's likely an environmental issue. (See https://lists.llvm.org/pipermail/llvm-dev/2020-October/145513.html for my previous investigation into the libunwind failures, where we determined they shouldn't be launch-blocking.)
> (It might be easier to give me SFTP access, to save Tobias the trouble of having to download and reupload to the SFTP.)
> On 10/7/20, 7:40 AM, "llvm-dev on behalf of Hans Wennborg via llvm-dev" <llvm-dev-bounces at lists.llvm.org on behalf of llvm-dev at lists.llvm.org> wrote:
> Hello once again,
> A few more issues appeared, so here is yet another release candidate:
> llvmorg-11.0.0-rc6 was just tagged.
> Source code and docs are available at
> Pre-built binaries will be added as they become ready.
> Please file reports for any bugs you find as blockers of
> Release testers, if you still have cycles, please take this for a
> quick spin. The changes from rc5 are minimal, and hopefully we can tag
> this as the final version very soon now.
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
More information about the Release-testers