similar to: [4.0.0 Release] Release Candidate 2 has been tagged

On Thu, Feb 9, 2017 at 2:23 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 9 Feb 2017, at 01:33, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> 4.0.0-rc2 was just tagged from the branch at r294535. > > Building on FreeBSD 10 at least didn't crash this time, and lld built just fine. :) I uploaded the following: >

Hi, I've just tagged the 4.0.1 -rc1 release. Testers can start testing and uploading the binaries. If you still have bug fixes you want to get into the 4.0.1 release, you have until May 22 to submit merge requests. -Tom

On 06/05/2018 10:47 AM, Dimitry Andric wrote: > On 4 Jun 2018, at 18:01, Tom Stellard via Release-testers <release-testers at lists.llvm.org> wrote: >> >> The 6.0.1-rc2 release has been tagged. Testers may begin testing and >> reporting results. > > Built for FreeBSD 10, tested and uploaded: > > SHA256 (clang+llvm-6.0.1-rc2-amd64-unknown-freebsd10.tar.xz)

On 31 Jan 2015, at 01:42, Hans Wennborg <hans at chromium.org> wrote: > Hi testers, > > 3.6.0-rc2 was just tagged. Please test and build binaries. > > The tracking bug for 3.6 blockers is http://llvm.org/pr22374. Please > file issues against it. > > Thanks for helping with the release! This time I got an error during check-all, on i386-unknown-freebsd10:

Hi testers, 3.6.0-rc2 was just tagged. Please test and build binaries. The tracking bug for 3.6 blockers is http://llvm.org/pr22374. Please file issues against it. Thanks for helping with the release! Hans

Hello testers, 5.0.0-rc4 was just tagged. There were very few changes after rc3, and if nothing unexpected comes up, this is what the final release will look like. Please test and let me know if there are any issues. Cheers, Hans

On Sat, Jan 31, 2015 at 9:24 AM, Dimitry Andric <dimitry at andric.com> wrote: > On 31 Jan 2015, at 01:42, Hans Wennborg <hans at chromium.org> wrote: >> Hi testers, >> >> 3.6.0-rc2 was just tagged. Please test and build binaries. >> >> The tracking bug for 3.6 blockers is http://llvm.org/pr22374. Please >> file issues against it. >>

Dear testers, 8.0.0-rc1 was just tagged (from the branch at r351980). It took a little longer than planned, but it's looking good. Please run the test script, share your results, and upload binaries. I'll get the source tarballs and docs published as soon as possible, and binaries as they become available. Thanks, Hans

Dear testers, Start your engines; 6.0.0-rc1 was just tagged. I know there are still open blockers and it's early in the process in a way, but I'd like to find out where we are. Please run the test script, let me know the results, and upload binaries. Thanks, Hans

Hi, I've tagged the 10.0.1-rc2 release, please test the release and report any issues. Thanks, Tom

Hello, When running test-release.sh using GCC 5.4.0 we encountered this error : /home/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/clang-tools-extra/clangd/Hover.cpp: In function ‘llvm::StringLiteral clang::clangd::{anonymous}::getNameForExpr(const clang::Expr*)’: /home/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/clang-tools-extra/clangd/Hover.cpp:450:10: error: could not convert

On Thu, Feb 8, 2018 at 10:43 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> There's been a lot of merges since rc1, and hopefully the tests are in >> a better state now. >> >> 6.0.0-rc2 was just tagged, after r324506. >> >>

Hello everyone, It took a bit longer than planned due to master being a somewhat unstable at the branch point, but Release Candidate 1 has now been tagged as llvmorg-10.0.0-rc1. Source code and docs are available at https://prereleases.llvm.org/10.0.0/#rc1 Pre-built binaries will be added there as they become available. Please file bug reports for any issues you find as blockers of

rc1 did not exhibit this mismatch. A repeat of the rc2 build repeated the mismatch. I diff'd the disassembly between phase 2 and phase 3 and the difference is the same on both builds. The difference follows: # diff x86isel_p{2,3}.s 2c2 < Phase2/Release/llvmCore-8.0.0-rc2.obj/lib/Target/X86/CMakeFiles/LLVMX86CodeGen.dir/X86ISelLowering.cpp.o: file format elf64-x86-64 --- >

Thanks! I'll get this posted on the web site. The "Performing Test ... failed to compile" failures from cmake are not interesting. But could you look in the log file and try to see what were the tests that failed in the "check-all" step? On Thu, Sep 12, 2019 at 4:39 PM Neil Nelson via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Xubuntu/Ubuntu 19.04,

Hi, 3.5.1-rc1 has been tagged, so it is time to begin testing. We can always use more testers, so if you would like to volunteer, let me know. For those that are new to testing, please review the documentation for how validate a new release: http://llvm.org/docs/ReleaseProcess.html Remember that when we check for regressions we want to compare the test results of 3.5.1-rc1 with 3.5.0-final.

It may be that the 'not' operator is not being found under bash at : 'RUN: at line 12';   not Perhaps this is would be better as the more commonly seen '!'. Neil Nelson On 9/13/19 12:12 PM, Neil Nelson via llvm-dev wrote: > > Toward the end of testing.9.0.0-rc4.log. > > Testing: 0 .. 10.. 20. > FAIL: Clang Tools :: clang-tidy/run-clang-tidy.cpp (17057 of

Dear testers, 5.0.0-rc1 has just been tagged. Please build, test and upload binaries to the sftp. Let me know if there are any issues. I'll upload sources, docs, and your binaries to the pre-release website once they're ready. Thanks, Hans

Hello testers, 4.0.0-rc3 was just tagged from the branch at r296762. This is a release candidate in the real sense: if no major issues show up with this one, it is the version that will be released. Please let me know if you find any issues, including in release notes or documentation, which will be on the pre-release web site later today. Please build, test, and upload binaries to the sftp

I've been building clang on linux for a couple of years now, contributing to the testing on Ubuntu, but this one has me stumped: fatal error: 'asm/socket.h' file not found #include <asm/socket.h> [1556/4006] Building CXX object projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.i386.dir/sanitizer_platform_limits_posix.cc.o FAILED: