similar to: [3.7.1 Release] -rc2 has been tagged

Hi, I just tagged 3.9.1-rc2, so testing can begin. There was a bug found in -rc1 before I could send out a release announcement, so I decided to merge the fix and tag -rc2 to save some testing cycles. We can always use more testers, so if you are interested in helping, let me know. Thanks, Tom

Hi, I have just tagged 3.7.1-rc1, so it is ready for testing. As a reminder, when doing regression testing, use the 3.7.0 release as your baseline. Thanks, 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 Thu, Jan 21, 2016 at 7:04 PM, Brian Cain via cfe-dev < cfe-dev at lists.llvm.org> wrote: > SuSE Linux Enterprise Server 11SP3 x86_64 > > Looks like I see several failures that weren't in 3.7.1. Is there any way > to tell whether these are regressions vs new-to-3.8.0-but-failing? The > MSan ones were in 3.7.1 but the ThreadPoolTest and the libc++ errors were > not

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

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

Hi, I've tagged LLVM 9.0.1-rc2. Testers can begin testing and uploading binaries. If all goes well, this will be the last -rc. -Tom

Should I expect the "-openmp" to work for this RC? I got a link error (only in phase 3?). Maybe the fact that it happened in phase 3 suggests some hardware malfunction of mine? Or are there tests executed on phase 3 that aren't attempted on earlier phases? $ CC=clang CXX=clang++ ./test-release.sh -release 3.7.1 -rc 2 -j1 -openmp -triple armv7l-ubuntu15.10-linux-gnueabihf ... cd

Hello everyone, 9.0.0-rc2 was tagged yesterday from the release_90 branch at r368683. In the Git monorepo it's available as the llvmorg-9.0.0-rc2 tag. Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc2 Binaries will be added as they become available. The tag went in roughly one week behind schedule (see "Upcoming Releases" at https://llvm.org), but

Hello everyone, 3.7-rc3 has just been tagged. Testers, please test, build binaries, upload to the sftp and report results to this thread. Again, a lot of patches got merged between rc2 and rc3, but hopefully nothing that should upset things. One thing that did change is that the release script now correctly symlinks clang-tools-extra into the build. If this causes problems on your platform,

Dear testers, 3.7.0-rc1 was just tagged; please start your testing engines :-) Upload binaries to the sftp and report your results to this thread. I'm sorry for the delay between branching and tagging. The changes to the release script took a little longer than I hoped. Thanks for helping with the release, and do let me know of any issues, questions, etc. The tracking bug for release

Hi everyone, 9.0.0-rc1 was just tagged from the release_90 branch at r367217 (tagged as llvmorg-9.0.0-rc1 in the Git monorepo). Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc1 Binaries will be added as they become available. Please file bug reports for any issues you find as blockers of https://llvm.org/PR42474 Release testers: please start your engines, run the

Hello everyone, 9.0.0-rc3 was tagged today from the release_90 branch at r370450. In the Git monorepo, it's tagged as llvmorg-9.0.0-rc3. Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc3 Binaries will be added as they become available. There are currently no open release blockers, which means if nothing new comes up, the final release could ship soon and this is

Hi, I've tagged the final version of 3.7.1. There is no difference from 3.7.1-rc2, so testers just need to build the packages no testing is required. -Tom

Here's the failing tests for rc2 on SLES11.3 (glibc 2.11, libstdc++4.7). I've done some amount of triaging what some critical elements of the failures are. Unabridged log is attached. Failing Tests (94): LLVM-Unit :: ExecutionEngine/Orc/OrcJITTests/DummyRPC.TestAsyncIntInt LLVM-Unit :: ExecutionEngine/Orc/OrcJITTests/DummyRPC.TestAsyncVoidBool LLVM-Unit ::

(cc'ing non-legacy llvm-dev this time; apologies if you get this twice. Please don't reply-all to the first one.) On Tue, Jan 19, 2016 at 3:47 PM, Hans Wennborg <hans at chromium.org> wrote: > Dear testers, > > Start your engines; 3.8.0-rc1 was just tagged from the 3.8 branch at > r258223. (It took a little longer than I'd planned, sorry about that.) > > There

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

Dear testers, 3.7.0-rc2 was just tagged. Please test, build binaries, upload to the sftp, and report results to this thread. A lot of fixes have been applied since rc1, both to the build script and the code in general, so hopefully it will be less bumpy this time. >From this point, I will no longer accept merge requests to finish existing features; it's now bug-fixes only. Thanks again

Hi, I've just tagged the 9.0.1-final release. Testers can begin uploading binaries. -Tom

Hello again, 9.0.0-rc4 was just tagged from the release_90 branch at r371490. In the Git monorepo, it's tagged as llvmorg-9.0.0-rc4. Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc4 Binaries will be added as they become available. There are not a lot of changes from rc3 to rc4, and there are again no open release blockers, so I'm hoping this will be the last