similar to: [3.8 Release] 'final' has been tagged

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, Release Candidate 2 has just been tagged [1]. Please build, test, and upload to the sftp. I know there are still outstanding issues from RC1, but there have been a lot of merges going into the branch and I think it's time for another round of RC testing. This RC comes a little behind schedule, sorry about that, but I'm still optimistic about hitting the target of releasing

Dear testers, 3.9.0-rc2 was just tagged from the 3.9 branch at r279183. This is a release candidate in the very real sense that if nothing new comes up, this is be what the final release looks like. There are currently no open release blockers, and no patches in my merge-queue. Please build, test, and upload binaries to the sftp. Let me know how everything goes. >From this point, the branch

Dear testers, 6.0.0-rc3 was just tagged, after r325901 on the branch. There are still a few open blockers, but I'm not sure we'll actually end up blocking on all of them. So depending on what comes up, this release candidate is probably pretty close to what the final release will look like (I'm still hoping for more release notes, though). I'm hoping we can get to

SLES11 binaries for rc3 uploaded. 55b63de8adc12c67eb11abcf1a5f7132cca59b4e clang+llvm-6.0.0-rc3-x86_64-linux-sles11.3.tar.xz On Fri, Feb 23, 2018 at 9:14 AM, Hans Wennborg via Release-testers < release-testers at lists.llvm.org> wrote: > Dear testers, > > 6.0.0-rc3 was just tagged, after r325901 on the branch. > > There are still a few open blockers, but I'm not sure

When I tested rc1 I found that some of the test suite wouldn't build on SLES11.3 as a consequence of changes to the tests. At least some of the msan tests have been changed leverage features of glibc newer than is available on this platform. I asked about a minimum-required glibc but didn't hear back. Is the minimum required glibc for 3.9 different from 3.8? When I tried rc1 on

I'm not aware of a bug filed for this, so please file one. I don't know much about the workings of test-suite myself, though. On Fri, Aug 11, 2017 at 2:54 PM, Brian Cain <brian.cain at gmail.com> wrote: > Much or all of "Bitcode/simd_ops/simd_ops_*.test" (254 failures) seem to be > failing for me with SIGILL. I'm guessing that my host CPU doesn't support

It's a test for the new interceptor for prlimit. It could be disabled with __GLIBC_PREREQ for 2.13+. On Fri, Aug 19, 2016 at 5:16 PM, Hans Wennborg <hans at chromium.org> wrote: > +Evgenii for msan. > > I suspect the community simply doesn't keep track of what glibc > version is required :-/ > > On Fri, Aug 19, 2016 at 5:10 PM, Brian Cain <brian.cain at

Dear testers, The final version of 8.0.0 was just tagged from the release_80 branch at r356364. It's identical to rc5 except for a few documentation changes. Apologies for being behind schedule. It took longer than planned this time. Please build the final binaries and upload to the sftp. For those following along: this means 8.0.0 is done, but it will take a few days to get all the

Hi, 5.0.2-final has been tagged. Testers may begin uploading binaries. Thanks, Tom

Ubuntu and SLES tarballs uploaded. I haven't had a chance to make a SLES12 build yet, but I will try in the coming days. f7553a0d66092ca0bbe1eab2af405523a18bafba clang+llvm-7.0.1-x86_64-linux-gnu-ubuntu-18.04.tar.xz 41db01a3b216df4fc22fae9c44e248889f9a01ed clang+llvm-7.0.1-x86_64-linux-gnu-ubuntu-16.04.tar.xz caf149635742622a3a5b220146ff34f9202b8670

Hi, I've just tagged 5.0.1-rc3, please test and report the results. Hopefully, this will be the last RC and the final release will be next week. -Tom

On 01/08/2019 11:36 AM, Ian Tessier via Release-testers wrote: > Can the ubuntu tarballs be published to the download site? They're not available yet. > These are up on the download site now. -Tom > On Mon, Dec 24, 2018 at 7:38 AM Brian Cain via cfe-dev <cfe-dev at lists.llvm.org <mailto:cfe-dev at lists.llvm.org>> wrote: > > Ubuntu and SLES tarballs

Dear testers, 8.0.0-rc3 was just tagged from the release_80 branch at r355015. We're running a little behind schedule now, but I think we're also close to be able to call this done. Please take a close look at this release candidate. Unless anything bad comes up, this is probably very similar to what the final release will look like. Testers, please run the test script, share your

Dear testers, 8.0.0-rc5 was just tagged from the release_80 branch at r355909. This is identical to rc4 with the addition of r355743. Hopefully it is the final release candidate, so please give it a good testing. As usual, please run the test script, share your results, and upload binaries. I'll publish source tarballs and docs as soon as possible, and binaries as they become available.

(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

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

Uploaded SLES11 and ubuntu 14.04. I can work on ubuntu 16.04 next. Is there any demand for ubuntu 17.10 releases? 4a0cb3e0ee573fb94e6c4f6be6c06eb661960471 clang+llvm-5.0.2-x86_64-linux-sles11.3.tar.xz 90430f7f0058100265352b1b2a2cd57e55558f92 clang+llvm-5.0.2-x86_64-linux-gnu-ubuntu-14.04.tar.xz On Thu, May 3, 2018 at 10:57 AM, Tom Stellard via Release-testers < release-testers at

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 28 Aug 2015, at 20:12, Hans Wennborg <hans at chromium.org> wrote: > > On Thu, Aug 27, 2015 at 6:46 PM, Hans Wennborg <hans at chromium.org> wrote: >> I have promoted RC4 to final; 3.7.0 has reached its final state. >> >> Thanks for all your hard work so far. Please build and upload binaries >> with "-final", and let's ship this next